You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't get compilation work by configuring the paths option for less-loader. And thus Less's preprocessing plugins (which may modify paths after they are installed) cannot work using less-loader.
For example, less-plugin-est injects some mixin code before compiling .less files and it also push its src directory into paths of the context. But after less-loader's WebpackFileManager taking over @import handling, Less stop searching paths for possible Less files.
The text was updated successfully, but these errors were encountered:
I'm currently refactoring that. You will be able to disable the WebpackFileManager by providing a paths array.
It will be disabled because we won't support both ways. Either you let Less resolve the imports via paths or you configure your paths in your webpack.config.js and let the WebpackFileManagerresolve it. Using both options does not make sense in my opinion.
I can't get compilation work by configuring the
paths
option forless-loader
. And thus Less's preprocessing plugins (which may modifypaths
after they are installed) cannot work usingless-loader
.For example,
less-plugin-est
injects some mixin code before compiling.less
files and it also push itssrc
directory intopaths
of the context. But afterless-loader
'sWebpackFileManager
taking over@import
handling, Less stop searchingpaths
for possible Less files.The text was updated successfully, but these errors were encountered: