Skip to content
This repository has been archived by the owner on Jul 24, 2024. It is now read-only.

Use true-case-path to fix re-entrancy issue on Windows #2149

Merged
merged 4 commits into from
Nov 11, 2017
Merged

Use true-case-path to fix re-entrancy issue on Windows #2149

merged 4 commits into from
Nov 11, 2017

Conversation

MLoughry
Copy link
Contributor

Fixes #1895

When using node-sass through multiple entry points (as can happen when using webpack) on Windows, the casing of the drive letter in the path can be inconsistent. Since Node is case-sensitive to a fault, this results in Node attempting to create a second instance of the native binding, which results in a Module did not self-register error.

The fix is to use true-case-path to normalize the binding path, to prevent unintended duplicate bindings from occurring.

@xzyfer
Copy link
Contributor

xzyfer commented Nov 11, 2017

Please remove the package-lock.json

@saper saper mentioned this pull request Nov 11, 2017
@MLoughry
Copy link
Contributor Author

package-lock.json is generated automatically by npm 5, so I've also added it to .gitignore

@xzyfer xzyfer merged commit 0a0f5c6 into sass:master Nov 11, 2017
@xzyfer
Copy link
Contributor

xzyfer commented Nov 11, 2017

Thanks!

@MLoughry
Copy link
Contributor Author

No problem. Is there a timeline for the next patch release? Currently this bug is blocking some development on my team.

@nealoke
Copy link

nealoke commented Nov 12, 2017

@MLoughry +1 for this annoying issue :)

@xzyfer
Copy link
Contributor

xzyfer commented Nov 12, 2017

Best estimate is some time this week

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

Successfully merging this pull request may close these issues.

Error: Module did not self-register
3 participants