Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Odd message from PostCSS
See original GitHub issueHas anyone else seen this while running critical?
Without from option PostCSS could generate wrong source map and will not find Browserslist config. Set it to CSS file path or to undefined to prevent this warning.
Issue Analytics
- State:
- Created 6 years ago
- Comments:9
Top Results From Across the Web
Using PostCSS Lost grid with SASS throws a weird message
I am trying to use Lost grid with SASS in my gulp workflow. I installed gulp-postcss, gulp-sass and lost grid from npm and...
Read more >Extends and standardize dependency message #1537 - GitHub
In most time developer need only dependency , it is very rare case when postcss plugin have own config file (i.e build-dependencies ),...
Read more >Postcss-cli error continue in version 0.97.3 - support - HUGO
version 97.2, displays an odd message that wasn't there before, indicating that post CSS isn't supported in this hugo version.
Read more >PostCSS API
Transform CSS with the power of JavaScript. Auto-prefixing, future CSS syntaxes, modules, linting and more are possible with hundreds of PostCSS plugins.
Read more >Add PostCSS to Create-React-App - DEV Community
Tagged with react, css, postcss, createreactapp. ... App { text-align: center; &-logo { animation: App-logo-spin infinite 20s linear; ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
You are completely right, I already had a standalone js file to call critical directly, for my own testing, and when I run that, I see the PostCSS warning message above, but only if inlineImages is turned on. It does seem like a bug in critical.
Glad you were able to get to the bottom of it! Let us know if you’re able to get the issue resolved upstream!