Implement eager postcss preprocessing#6
Conversation
| code: await this.postcss.process(content, { from: undefined }) | ||
| }; | ||
| } | ||
| if (this.postcss && (!attributes.lang || attributes.lang === 'postcss')) { |
There was a problem hiding this comment.
For version 2 of melte-compiler, we should remove the checks for attribute.lang and always run postcss to match what svelte-preprocessor does (it runs the preprocessor for the lang if there is one, and then runs postcss).
To avoid introducing a backwards breaking change now, could we add an option for this behaviour?
There was a problem hiding this comment.
Sure, that's what I suggested in #5
What would you like the config option to be named? I'm happy to update the PR.
There was a problem hiding this comment.
I'm not sure what a good name would be. Maybe something like alwaysUsePostCSS?
|
Meteor 2.6.1 adds built-in support for postcss in its I'm thinking of deprecating melte's postcss integration, and instead recommending disabling the |
Uses PostCSS preprocessing, if
postcssis configured & available and there is no conflictinglangattribute present in the<style>tag.Fixes #5