Provide support for lesscss plugins#40
Conversation
|
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 |
yes. If you want to be perfect allow to choose the key in the options by query parameter. This way you could avoid conflicts. |
That would be the 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 |
Provide support for LESS plugins
|
Nice! Good work 👍 Shipped with |
|
Thanks! Glad I could help. |
Since version 2 of less, Clean CSS is no longer bundled but has to be used as a plugin http://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.