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

win32 not supported #6

Closed
doivosevic opened this issue Dec 4, 2014 · 3 comments
Closed

win32 not supported #6

doivosevic opened this issue Dec 4, 2014 · 3 comments
Assignees
Labels

Comments

@doivosevic
Copy link

54 error notsup Unsupported
54 error notsup Not compatible with your operating system or architecture: jfum@1.0.2
54 error notsup Valid OS: !win32
54 error notsup Valid Arch: any
54 error notsup Actual OS: win32
54 error notsup Actual Arch: x64
55 error System Windows_NT 6.2.9200
56 error command "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "i"
57 error cwd C:\Users\Dito\Desktop\proj\Atilax
58 error node -v v0.10.33
59 error npm -v 1.4.28
60 error code EBADPLATFORM
61 verbose exit [ 1, true ]

why is node-jfum not supporting win32?

@Starefossen
Copy link
Contributor

Hi @DominikDitoIvosevic,

Thanks for pointing this out. The original version had dependencies not compatible with win32. However the newest version should be win32 compatible, it is however untested on that particular platform. I will push an new version to NPM asap to fix this.

@Starefossen Starefossen added the bug label Dec 4, 2014
@Starefossen Starefossen self-assigned this Dec 4, 2014
@Starefossen
Copy link
Contributor

Version v1.0.3 of jfum is now on npm, it should solve this problem.

@doivosevic
Copy link
Author

Yeah, it works, thanks 👍

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

No branches or pull requests

2 participants