postcss-cli do not copy folder structure from input files when pattern is used about postcss-cli HOT 18 CLOSED

Not in favor of that; since the --ext option will only be used in a few cases. Also would be confusing upgrading from v2.

from postcss-cli.

👋 Do you see a red logo when postcss -v

from postcss-cli.

@michael-ciniawsky Yep. It says 2.6.0.

from postcss-cli.

Version printed should still display 2.6.0 since it's not updated yet

from postcss-cli.

I see.

from postcss-cli.

When you see the red postcss logo you are on v3@beta :) Place the postcss.config.js in the root of your project for getting started

from postcss-cli.

I tried with just postcss --use precss src/**/*.pcss --dir out/ but still got Cannot find module 'src/**/*.pcss'

from postcss-cli.

@aesopturtle Try postcss src/**/*.pcss --use precss --dir out/

from postcss-cli.

@RyanZim That works! :D
But it still doesn't copy the folder structure. All files in subfolders are output under the same folder (out/) and the extension remains pcss.

from postcss-cli.

So there are 2 issues here:

1. The output doesn't have the same folder structure as the input when used with pattern.
2. I don't seem to be able to specify the output file extension when using --dir.

1. This is a known issue with both v2 & the development version; issue is here: #30.
2. Opened a new issue for that here: #79.

from postcss-cli.

As far as I remember, if the input has multiple files, either -d or -r must be specified, right? How about... if -d or -r is not specified, we output at its own folder?

from postcss-cli.

@RyanZim Thanks :)

from postcss-cli.

As far as I remember, if the input has multiple files, either -d or -r must be specified, right? How about... if -d or -r is not specified, we output at its own folder?

@aesopturtle Not sure what you mean; what would the files be named?

from postcss-cli.

@RyanZim The output file should have the same name but with an extension following --ext(?) option.

from postcss-cli.

@ai Are options an the result {Object} ?
@RyanZim Maybe we can use it for getting the dirname from options.from or otherwise I need to find something else

from postcss-cli.

@michael-ciniawsky 😕 What are you trying to say?

from postcss-cli.

For nested output directory support we need to get the dirname of the src/**/*.css glob => /**/ somewhere, just thinking out loud where :D at best

from postcss-cli.

@michael-ciniawsky Here was a PR for v2: #31. That may give you some ideas.

At any rate, I'm going to close this issue since discussion has moved elsewhere.

@michael-ciniawsky If you want to do more thinking out loud, do it on gitter, there are plenty of helpful people there. 😉

from postcss-cli.