node js ipfs on windows

[nezzard]

Hi, i'm tried to install ipfs from npm on windows 10, but i always get an errors. So i have question, can i install ipfs on windows, or it's only for linux?

[victorb]

Don't think there is something that should stop it from working, but not sure how well tested js-ipfs is on windows. It'll help a lot of you post a full log of the errors and also the output from npm version

[nezzard]

npm: '3.10.10', ares: '1.10.1-DEV', http_parser: '2.7.0', icu: '58.2', modules: '48', node: '6.10.3', openssl: '1.0.2k', uv: '1.9.1', v8: '5.1.281.101', zlib: '1.2.11' }

And npm install log
https://pastebin.com/r87NqUHe

And
jsipfs --help C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42 throw new Error(Invalid key: ${this.toString()}`)
^

Error: Invalid key: \SHARDING
at new Key (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\interface-datastore\src\key.js:42:13)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\sharding.js:12:18)
at Module._compile (module.js:570:32)
at Object.Module._extensions..js (module.js:579:10)
at Module.load (module.js:487:32)
at tryModuleLoad (module.js:446:12)
at Function.Module._load (module.js:438:3)
at Module.require (module.js:497:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\Yura\AppData\Roaming\npm\node_modules\ipfs\node_modules\ipld-resolver\node_modules\datastore-core\src\index.js:5:27)`

[daviddias]

Hi @nezzard, thanks for reporting. This is a known issue with some proposed PR changes:

• fix: use os specific path separator interface-datastore#5
• Windows Support - Fix for platform inconsistency of path.normalize interface-datastore#6

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

[nezzard]

I tried to make fix from ipfs/interface-datastore#5 but nothing work, i have the same error like before

[mkg20001]

Wanna help us fix this issue? I need to get a Windows VM set up and won't have fast enough connectivity this week to download the full image.

Or you can try https://www.appveyor.com/

[daviddias]

There has been a fixed pushed, merged and released for interface-datastore. Could you confirm if this works now for you?

[nezzard]

Just npm install ipfs?
If yes, it's not working

[daviddias]

Oh, that is because I never released the new interface-datastore, shame on me. Try again now :)

[nezzard]

Did npm uninstall ipfs than install and now get the same error Invalid key: \SHARDING

[download13]

Hey, I'd really like to help get js-ipfs running on windows.

To that end I made a pull request to update the dependency of a dependency of this project: ipld/js-ipld#83

Once that's merged and published the dependency version on here can be updated and we can start looking at whatever the next windows-related bug will be.

[daviddias]

@download13 which version of npm are you using? You shouldn't have this issue since interface-datastore was published as a patch version and ipld-resolver is using semver for that dep.

Could you try doing a fresh npm install on this repo?

[download13]

I tried it just now. Still getting

Error: Invalid key: \SHARDING
    at new Key (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\node_modules\interface-datastore\src\key.js:42:13)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\sharding.js:12:18)
    at Module._compile (module.js:571:32)
    at Object.Module._extensions..js (module.js:580:10)
    at Module.load (module.js:488:32)
    at tryModuleLoad (module.js:447:12)
    at Function.Module._load (module.js:439:3)
    at Module.require (module.js:498:17)
    at require (internal/module.js:20:19)
    at Object.<anonymous> (C:\Users\download\Desktop\js-ipfs\node_modules\datastore-core\src\index.js:5:27)

[download13]

Isn't this using a package-lock.json file? I thought you had to update them somehow as the dependencies specified there will always be installed.