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

Webpack module imports using "~" are broken #131

Closed
raypatterson opened this issue Jul 27, 2015 · 3 comments
Closed

Webpack module imports using "~" are broken #131

raypatterson opened this issue Jul 27, 2015 · 3 comments

Comments

@raypatterson
Copy link

Hi,

I recently upgraded from 0.4.2 to 1.0.3 and module imports stopped working.

Downgrading back to 0.5.0 works but am unable to test 0.6.0 due to this threading issue.
(The process.env.UV_THREADPOOL_SIZE = 100; workaround doesn't work for 0.6.0 but does for 1.0.3).

The CSS output includes the correct resource paths within the imports but not the file contents.

@import url(/absolute/path/to/file/in/node_modules/disk/filename.sass);

My webpack config uses:

{ 
    ...
    "autoprefixer-loader": "^2.0.0",
    "css-loader": "^0.15.6",
    "extract-text-webpack-plugin": "^0.8.2",
    "sass-loader": "^0.5.0",
    "style-loader": "^0.12.3",
    "webpack": "^1.10.5",
    ...
}

Not sure if this is related to #108 or if it's an issue with node-sass itself.

Any insight would be appreciated!

@jorrit
Copy link
Contributor

jorrit commented Jul 28, 2015

Can you publish a small repository with this problem?

@jhnns
Copy link
Member

jhnns commented Aug 5, 2015

Could you guys check out the current master branch and check if it works for you? I've heavily refactored the import mechanism and need more tests.

@jhnns
Copy link
Member

jhnns commented Aug 6, 2015

Should be fixed with 2.0.0

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