-
Notifications
You must be signed in to change notification settings - Fork 147
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
npm run start #8
Comments
Did you |
Yes.
But then it goes through what looks a normal install. |
Same issue, can't seem to run it on Windows 10. Really cool project though. |
λ npm install |
I was experiencing some issues running I am using Node 4.3.1. Hopefully this helps. |
Thanks. That does help. Not going to reinstall Python 2.7 (upon having 3.5 at this moment to run it though honestly. Appreciate finally at least undertanding how to potentially make it run. I've been experimenting a little bit with BASH on windows, hopefully that makes this process easier, because Node Gyp / FSevents stuff on Windows 10 is hellish. |
I ported the project to React (dropped Node support), updated the code and built an online editor on top of it, if you are interested in running the app in the browser you can play with https://github.com/sonaye/react-color-wander. |
Hi Sonaye. Any chance you can make the code for react-color-wander public? I'd love to take a look at it. Thanks. |
Hi @sonaye 👋 Would you mind making the repo you reference public? |
Hey @sampsojp @cujarrett, here is a backup copy of that repo react-color-wander-master.zip |
@sonaye - Thank you very much! |
'npm run start' returns this:
(node:37226) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:37226) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:37226) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
(node:37226) fs: re-evaluating native module sources is not supported. If you are using the graceful-fs module, please update it to a more recent version.
sh: budo: command not found
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "start"
npm ERR! node v6.1.0
npm ERR! npm v3.8.6
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! [email protected] start:
budo browser.js:bundle.js --live -- -t babelify
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the [email protected] start script 'budo browser.js:bundle.js --live -- -t babelify'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the color-wander package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! budo browser.js:bundle.js --live -- -t babelify
npm ERR! You can get information on how to open an issue for this project with:
npm ERR! npm bugs color-wander
npm ERR! Or if that isn't available, you can get their info via:
npm ERR! npm owner ls color-wander
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! /Users/kylewagner/Desktop/color-wander/npm-debug.log
The text was updated successfully, but these errors were encountered: