-
-
Notifications
You must be signed in to change notification settings - Fork 430
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
Use custom importer #31
Comments
I'll be excited to see a prototype of this. I want to modularize my code into different node modules, but I can't do that if |
ohhhh great - was about to ask for this. |
node-sass just implemented the api (sass/node-sass#530). Now we need to wait for v2 to be released. |
Which currently is waiting for a lib-sass release (sass/libsass#697) :P Sounds like it'll all happen soon though, thank you! |
Is this now working? Or is there more to do with setting up sass-loader to @import from node_modules etc. Would be keen to test it out (I could just depend on the repo, rather than npm, I guess) if it's ready. |
Nope, we need to adjust the sass-loader for this. But I guess it's ready to be implemented 😬 |
@jhnns @haustraliaer see above PR. |
🎉 Thanks everyone! Works like a dream. |
Just wanted to point out that custom importers have been implemented with sass/libsass#21. They are currently being tested and it will take some time until node-sass provides an api, so it's still a way to go.
With custom importers we're able to plug-in webpack's resolving algorithm.
The text was updated successfully, but these errors were encountered: