-
Notifications
You must be signed in to change notification settings - Fork 1.2k
'npm install ipfs' fails on Windows 10 if Windows login (and user's home path) contains non-ASCII characters #1318
Comments
Does other packages work to install globally but not js-ipfs? Also, could you paste the full output of your installation log here please? |
Yes, I'm able to install other packages globally. Here is the console output:
|
Honestly, you're probably going to have other issues too. This library makes assumptions about linux style paths in a lot of places. I am using windows at home also and I have to use new WSL to get it to work. So I would just say use that for now. |
This is a little old but I don't think its fundamentally changed that much: |
I haven't heard about WSL feature earlier. |
Is this still an issue with latest js-ipfs? Can anyone confirm? |
Unfortunately yes
Last line declares that something is updated, but we see same errors from gyp saying it can't find 'node.h'. |
@hacdias Can you test with latest js-ipfs? Or @aschmahmann? |
Is this problem specific to IPFS or does it happen with any module that has a native module as a dependency? |
It looks like its in the Looking at the way it builds it looks pretty standard, it seems like it should work on windows with unicode path characters. Try installing some other native module like As a workaround, if you move your code to |
|
If this is still an problem an issue should be opened against npm. |
Version:
js-ipfs version: 0.28.2-
Repo version: 6
System version: x64/win32
Node.js version: v8.11.1
Platform:
Windows 10 Home edition 64 bit
Type:
High
Description:
Unable to install js-ipfs via npm on Windows 10 in case user's login and/or user's home path (c:\Users\[Username]) contains non-ASCII characters.
Steps to reproduce the error:
As a result you see errors produced by node-gyp compilati telling 'node.h' not found etc.
The text was updated successfully, but these errors were encountered: