Provide documentation link for the warning ` Using a JavaScript PostCSS config file means losing out on caching features of Parcel. Use a .postcssrc(.json) file whenever possible.`
See original GitHub issue🙋 feature request
I’m using Tailwind and Parcel 2 and every time I build I get this warning: Using a JavaScript PostCSS config file means losing out on caching features of Parcel. Use a .postcssrc(.json) file whenever possible.
However, when I delete the config file Tailwind no longer works.
Please will you add more detail to this warning, or a link to some Parcel documentation explaining what we have to do here to make it work.
Even a comprehensive answer in this issue would probably help people like me who are googling this warning and finding nothing 😦
Issue Analytics
- State:
- Created 3 years ago
- Reactions:6
- Comments:6 (4 by maintainers)
Top Results From Across the Web
How do I solve error : "@parcel/transformer-postcss
@parcel/transformer-postcss: PostCSS config must have plugins at load ... file means losing... Use a .postcssrc json file whenever possible).
Read more >CSS - Parcel
You can use PostCSS with Parcel by creating a configuration file using one of these names: .postcssrc , .postcssrc.json , .postcssrc.js , or...
Read more >Advanced Features: Customizing PostCSS Config - Next.js
Warning : When you define a custom PostCSS configuration file, Next.js completely disables the default behavior. Be sure to manually configure all the ......
Read more >Adam Wathan on Twitter: "I can't seem to get `postcss.config.js ...
config.js` files working in ESM Next projects If I use `postcss.config.cjs` the file is ignored, but if ...
Read more >@parcel/transformer-postcss NPM | npm.io
Out of the box support for JS, CSS, HTML, file assets, and more - no plugins to install. Automatically transforms modules using Babel,...
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

Instead of something postcss.config.js
you should add a .postcssrc with:
Babel’s
envproperty in config files is great for this:Unfortunately PostCSS doesn’t have something like this (yet)