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 config not working #10099

Closed
razonyang opened this issue Jul 17, 2022 · 4 comments
Closed

PostCSS config not working #10099

razonyang opened this issue Jul 17, 2022 · 4 comments

Comments

@razonyang
Copy link
Contributor

resources.Get "assets/main.css" | resources.PostCSS (dict "config" "mypostcss.config.js")

mypostcss.config.js as follows:

throw new Error('error from mypostcss.config.js');

Hugo does check the config exists, but didn't use it.

What version of Hugo are you using (hugo version)?

$ hugo version

$ hugo version
hugo v0.101.0-466fa43c16709b4483689930a4f9ac8add5c9f66+extended linux/amd64 BuildDate=2022-06-16T07:09:16Z VendorInfo=gohugoio

Does this issue reproduce with the latest release?

Yes.

@bep
Copy link
Member

bep commented Jul 17, 2022

What's the output of hugo -v?

@bep bep added this to the v0.102.0 milestone Jul 17, 2022
@bep
Copy link
Member

bep commented Jul 17, 2022

OK, I think I remember now, your docs update is correct; this did as intended in an older PostCSS version, though.

@bep bep added the Upstream label Jul 17, 2022
@bep
Copy link
Member

bep commented Jul 17, 2022

I'm closing this in favour of the docs issue.

@bep bep closed this as completed Jul 17, 2022
@github-actions
Copy link

github-actions bot commented Aug 8, 2022

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 Aug 8, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants