-
-
Notifications
You must be signed in to change notification settings - Fork 7.4k
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
Expose underlying error messages for postcss #9730
Comments
Oh man, I know exactly how you feel. I am dealing with this same error right now, and have found 3 different root causes and suggested fixes online for it. Unfortunately, none of them fixed my problem. I hoped that turning on |
I'm getting this exact same error message, and I haven't been able to get to the bottom of it:
|
You are using nvm, so I am suspicious of environment variables. Hugo's default security policy with v0.115.2 and later allows access to this predefined list of environment variables:
Please change this to:
And test again. To allow access to all environment variables:
|
How to force hugo to use the postcss that is installed?I am seeing this same error, adding an entry to the security.exec block had no effect.
Since I am at kitchen sink stage of troubleshooting I will include this pipeline log snippet w
|
@jmooring I tried both of the above. No change... I'm also using
Any other ideas? |
Let's continue to troubleshoot elsewhere. Please create a topic on the forum, and be prepared to share your project repository, privately if you wish. |
When using the extended binary with postcss, I wonder if there's a way the error messages can be improved in some scenarios. I've spent some time today a little puzzled with this error message:
After triple-checking I was using hugo extended, and had the node modules installed, I dug into the hugo source code and my issue was actually due to not having
npx
on my path (node/npm were). It looks like any errors with the npx call get handled as if postcss is not supported.It'd be great if we could get something like:
where
npx: not found
is what I get when I try from a shell.The text was updated successfully, but these errors were encountered: