Parcel: Exclude styles from PostCSS

[johanbaath]

I have some legacy .less files that I have to import, but it seems they are passed through PostCSS as well. Is there any way to disable this behaviour? I still want to use PostCSS for my regular .css files.

[davidnagli]

Why don’t you want the .less files to be passed through PostCSS?

[johanbaath]

In my case it's because PostCSS reports some errors that it can't parse in that file. I'm importing .less files from Ant Design which I have customized some variables for:

384px - 16px 24px * 2 - 24px - 48UL', 'DIV', 'RPAREN', got 'LENGTH'
-------------^
Expecting 'EOF', 'ADD', 'SUB', 'MUL', 'DIV', 'RPAREN', got 'LENGTH'

Since I use cssnext it fails in: postcss-calc. It would just be easier for me to skip PostCSS for this file I guess 😃 .

[nouh]

@johanbaath I also use ant design. how did you solve less preprocessing with parcel

[devongovett]

hmm, shouldn't less process those variables first before passing to postcss?

[devongovett]

Closing due to inactivity. Please feel free to re-open if you still have an issue.

[npup]

Hello!
I have a case in an app where I need to process a secondary entry point (scss file) and have it produce a separate file _untampered with_ by postcss. At first I tried to use multiple entry points for the build, but to get my head around it I fell back to two passes instead.
The problem for me now is that the settings in .postcssrc (using modules) of course are picked up _also for the secondary pass_, while I would like it to just be converted to CSS, class names intact.

Not sure if I want a feature added to parcel or if I just need some help here :-)

[kidandcat]

I'm looking for this too, need to exclude some css files from processing at all for a big legacy project.

In my case is because the css class names are being dynamically generated and applied to elements from javascript.