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

fix EINVAL error throwed by memory-fs on Windows #71

Merged
merged 3 commits into from
Nov 10, 2017
Merged

fix EINVAL error throwed by memory-fs on Windows #71

merged 3 commits into from
Nov 10, 2017

Conversation

dangh
Copy link
Contributor

@dangh dangh commented Oct 27, 2017

Since we use POSIX style prefix /assets, we need to resolve it as POSIX style as well otherwise memory-fs will normalize it to an invalid path (eg. \\assets\\vendor.js) and raise EINVAL error on Windows.

Fixes #9

Since we use POSIX style prefix `/assets`, we need to resolve it as POSIX style as well otherwise memory-fs will normalize it to an invalid path on Windows and raise exception.

Fixes #9
@prasanthkarukkuvel
Copy link

prasanthkarukkuvel commented Nov 10, 2017

Any progress on this ?, we need this fix :)

@asfktz
Copy link
Owner

asfktz commented Nov 10, 2017

Thanks for the fix, @dangh!

I apologize for the long wait. I'll merge it now.

@asfktz asfktz merged commit ff89132 into asfktz:master Nov 10, 2017
@asfktz
Copy link
Owner

asfktz commented Nov 10, 2017

Just released a new version with a fix (0.3.4) @dangh @prasanthkarukkuvel

@dangh dangh deleted the fix-memory-fs-path-on-windows branch November 18, 2017 18:23
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

Successfully merging this pull request may close these issues.

test 'createMemory should have bundles' failing on Windows
3 participants