-
Notifications
You must be signed in to change notification settings - Fork 29
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
Supplying custom parsers through the compiler.compile opts #86
Comments
@akmoulai sorry, not in v2. I'm working in a complete rewrite for v3 which will support this and other features. Currently, the compiler API is convoluted and inconsistent, I hope v3 will be more simple and versatile. |
@aMarCruz Thanks for your feedback, closing the issue... Please let me know if you would consider a PR! |
@GianlucaGuarini I'd really like to set my parsers through It'd be really easy to add this feature by merging whatever |
After searching a quite a bit, the only way I found to pass custom CSS parsers was to use
riot.parsers.css.myCustomCSSParser
which is fine if you have access to theriot
's instance.However, I'm in a situation where we use esnunes/riotjs-loader and I have no way to modify riot's instance. The only thing I can pass through with webpack is the
options
for thecompiler.compile
function (done through thequery
object in webpack).Do you think you could make supplying new custom parsers definitions through the opts?
Something like:
There may be other useful use cases (I'm new to Riot).
@GianlucaGuarini @aMarCruz Thanks for considering !
Edit: the need for this is to add
postcss
autoprefixer
to SCSS styles defined in the tags. All of that with webpack!The text was updated successfully, but these errors were encountered: