-
-
Notifications
You must be signed in to change notification settings - Fork 429
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
fix: resolving of scoped npm packages #447
fix: resolving of scoped npm packages #447
Conversation
@vanesyan thanks 👍 |
Any updates on the thread? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@vanesyan Thx
/cc @jhnns friendly ping |
Any chance someone could get this merged? This is actually going to be a growing issue as more people start trying to bundle |
@sirlancelot - contrib was created to allow Tobias and other core member focus on Webpack. If you need to get a hold of someone, try the lead maintainer ( for repos like sass-loader that have one ) For other libs in If none of that works, DM me on gitter or twitter. |
@michael-ciniawsky - I'm working on that now, i'll get this sorted shortly. |
Thanks @d3viant0ne, I hadn't realized others were maintaining this. Thanks so much for you contributions! |
Can you also, please, upstream fix on npm?! :) |
Hello @d3viant0ne, @bebraw, @vanesyan! This worked fine with sass-loader 6.0.3 To make it work with sass-loader 6.0.4 I had to write |
Yes, it seems that with landed pr sass-loader preventing from processing file formatting, (e.g. adding underscore and file extension on lines 42-47) Should be fixed... |
Also breaking my build for the same reason. |
Fix #424