Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

PostCSS 6 is broken, use PostCSS 5 #5001

Closed
budparr opened this issue Jul 26, 2018 · 5 comments
Closed

PostCSS 6 is broken, use PostCSS 5 #5001

budparr opened this issue Jul 26, 2018 · 5 comments

Comments

@budparr
Copy link

budparr commented Jul 26, 2018

In 0.44 you can specify an alternative config file name:

"config" "./postcss.config.ALTERNATE.js"

In 0.45, the above setting throws the following PostCSS error, indicating there is no config file:

You did not set any plugins, parser, or stringifier. Right now PostCSS do nothing. Pick plugins for your case on https://www.postcss.parts/ and usemthem in postcss.config.js.

I've put a test case here: https://github.com/budparr/hugo-issue-5001

note that if you merely specify the wrong path, you get the config not found error from Hugo, not the PostCSS error.

@bep
Copy link
Member

bep commented Jul 26, 2018

We certainly have a potential for improvement in the test department here ...

Relevant changes in Hugo 0.45 for anyone wanting to debug this:

  • We use local postcss if installed
  • We read configfile from project or theme

@bep
Copy link
Member

bep commented Jul 26, 2018

"config" "./postcss.config.ALTERNATE.js"

You may want to test without the "./" prefix.

@budparr
Copy link
Author

budparr commented Jul 26, 2018

I did that and all sorts of other iterations. Thanks

@bep bep added the Upstream label Jul 27, 2018
@bep bep changed the title PostCSS config won't use alternate filename in v0.45+ PostCSS 6 is broken, use PostCSS 5 Jul 27, 2018
@budparr
Copy link
Author

budparr commented Jul 27, 2018

I'll close this as it's explained in postcss/postcss-cli#233

@budparr budparr closed this as completed Jul 27, 2018
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Feb 28, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants