GrapesJS / grapesjs

Free and Open source Web Builder Framework. Next generation tool for building templates without coding
https://grapesjs.com
BSD 3-Clause "New" or "Revised" License
22.38k stars 4.06k forks source link

Can't install with npm on Windows 10 #95

Closed kedrzu closed 7 years ago

kedrzu commented 7 years ago

Having some troubles installing grapejs on windows 10 using NPM. There is somewhere dependency to fsevents that is not optional and requires darwin OS. That causes installation to fail.

npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.0.0 (node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN aurelia.skeleton.aspnetcore@1.0.0 No description
npm WARN aurelia.skeleton.aspnetcore@1.0.0 No repository field.
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "grapejs" "--save"
npm ERR! node v7.10.0
npm ERR! npm  v4.2.0
npm ERR! code EBADPLATFORM

npm ERR! notsup Unsupported platform for fsevents@1.0.12: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm ERR! notsup Valid OS:    darwin
npm ERR! notsup Valid Arch:  any
npm ERR! notsup Actual OS:   win32
npm ERR! notsup Actual Arch: x64

npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\kedrzu\AppData\Roaming\npm-cache\_logs\2017-05-27T11_48_54_420Z-debug.log

Note, that there is also a warning corresponding to an optional dependency do fsevents of other version.

Thanks for all help!

artf commented 7 years ago

Sorry @kedrzu, but It's not related to GrapesJS itself, so can't help you here. You can check webpack/webpack#1435 which is basically the same issue but has more info about. Seems also that npm install --no-optional solves the problem

lock[bot] commented 5 years ago

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.