Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork198
Provide support for lesscss plugins#40
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
jhnns commentedMar 19, 2015
You're right. It's better to use the webpack options in this case (although it's usually discouraged). What do you think@sokra? Could you namespace and rename the option key to module.exports={lessLoader:{lessPlugins:[...]}}; We never used the term |
sokra commentedMar 19, 2015
yes. If you want to be perfect allow to choose the key in the options by query parameter. This way you could avoid conflicts. |
jhnns commentedMar 19, 2015
That would bethe perfect solution™ indeed 😀. But it should use a sane default like the npm name camelcased. Something like: require("!less-loader?config=someCustomName!./main.less") module.exports={someCustomName:{lessPlugins:[...]}}; And |
mfellner commentedMar 22, 2015
jhnns commentedMar 22, 2015
Nice! Good work 👍 Shipped with |
mfellner commentedMar 22, 2015
Thanks! Glad I could help. |
Since version 2 of less, Clean CSS is no longer bundled but has to be used as a pluginhttp://lesscss.org/usage/#command-line-usage-compress. The query-string configuration of less-loader is insufficient to pass plugin instances to less.
This change allows for plugins to be passed to less as specified here:http://lesscss.org/usage/#plugins-using-a-plugin-in-code.