Skip to content
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

Less's paths option seem to be ignored when using less-loader #168

Closed
Justineo opened this issue Mar 17, 2017 · 1 comment
Closed

Less's paths option seem to be ignored when using less-loader #168

Justineo opened this issue Mar 17, 2017 · 1 comment

Comments

@Justineo
Copy link

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.

@jhnns
Copy link
Member

jhnns commented Mar 17, 2017

Thanks for reporting this.

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.

Previous discussions:

#75
webpack-contrib/sass-loader#307

and probably more I don't remember now 😁

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants