npm start -s fails - Githubissues

BostjanSkok commented 8 years ago

Node version: v6.3.1 npm version: 3.10.3 Operating system: ubuntu:xenial docker container Command line used:

root@5a5d40d8a0d3:/FrontEnd# npm start -s sh: 1: rimraf: not found sh: 1: babel-node: not found ERROR: "remove-dist" exited with 1.

Steps to reproduce:

coryhouse commented 8 years ago

Interesting OS story. It sounds like your path isn't getting set.

Two things:

You ran npm install first, right?
Try adding the path in front of all calls to node modules in the scripts in package.json. For example:

node_modules/.bin/babel-node

or

./node_modules/.bin/babel-node

BostjanSkok commented 8 years ago

my ./node_modules/.bin/ root@5d4645625f4b:/FrontEnd# ls -l /FrontEnd/node_modules/.bin/ total 0 lrwxrwxrwx 1 1000 1000 0 Aug 11 13:43 acorn -> ../acorn/bin/acorn lrwxrwxrwx 1 1000 1000 0 Aug 11 13:43 eslint -> ../eslint/bin/eslint.js lrwxrwxrwx 1 1000 1000 0 Aug 11 13:49 npm-run-all -> ../npm-run-all/bin/npm-run-all/index.js lrwxrwxrwx 1 1000 1000 0 Aug 11 13:50 run-p -> ../npm-run-all/bin/run-p/index.js lrwxrwxrwx 1 1000 1000 0 Aug 11 13:50 run-s -> ../npm-run-all/bin/run-s/index.js

i ran: $npm run setup $npm start -s

npm-run-all not found so i ran $ npm install npm-run-all -g

Now npm start -s
sh: 1: babel-node: not found sh: 1: rimraf: not found ERROR: "start-message" exited with 1.

without the -s if it helps:

sh: 1: sh: 1: rimraf: not found babel-node: not found

npm ERR! Linux 3.13.0-92-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run-script" "start-message" npm npmERR! node v6.3.1 npmERR! ERR! npm Linux 3.13.0-92-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "run-script" "remove-dist" npm ERR! v3.10.5 npm node v6.3.1 ERR!npm file sh npm ERR! ERR! code ELIFECYCLE npm npm ERR! errno ENOENT npm v3.10.5 ERR!npm syscall spawn ERR! filenpm sh npm ERR! ERR! micro-comb-ui@0.1.0 start-message: babel-node tools/startMessage.js codenpm ELIFECYCLE ERR!npm ERR! spawn ENOENT npm errno ENOENT npm ERR! syscallERR! spawn npm npm ERR! ERR! micro-comb-ui@0.1.0 remove-dist: rimraf ./dist npm Failed at the micro-comb-ui@0.1.0 start-message script 'babel-node tools/startMessage.js'. npmERR! spawn ENOENT ERR! Make sure you have the latest version of node.js and npm installed. npm npm ERR! If you do, this is most likely a problem with the micro-comb-ui package, npmERR! npm ERR! not with npm itself. ERR!npm ERR! Failed at the micro-comb-ui@0.1.0 remove-dist script 'rimraf ./dist'. npm Tell the author that this fails on your system: npm ERR!ERR! babel-node tools/startMessage.js Make sure you have the latest version of node.js and npm installed. npm ERR! You can get information on how to open an issue for this project with: npm npm ERR!ERR! npm bugs micro-comb-ui If you do, this is most likely a problem with the micro-comb-ui package, npmnpm ERR!ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: Or if that isn't available, you can get their info via: npmnpm ERR! npm owner ls micro-comb-ui npm ERR!ERR! rimraf ./dist npm There is likely additional logging output above. ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs micro-comb-ui npm ERR! Or if that isn't available, you can get their info via:

npm ERR! npm owner ls micro-comb-ui npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /FrontEnd/npm-debug.log

npm ERR! Please include the following file with any support request: npm ERR! /FrontEnd/npm-debug.log ERROR: "start-message" exited with 1.

npm ERR! Linux 3.13.0-92-generic npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start" npm ERR! node v6.3.1 npm ERR! npm v3.10.5 npm ERR! code ELIFECYCLE npm ERR! micro-comb-ui@0.1.0 prestart: npm-run-all --parallel start-message remove-dist npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the micro-comb-ui@0.1.0 prestart script 'npm-run-all --parallel start-message remove-dist'. 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 micro-comb-ui package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! npm-run-all --parallel start-message remove-dist npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs micro-comb-ui npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls micro-comb-ui npm ERR! There is likely additional logging output above.

npm ERR! Please include the following

coryhouse commented 8 years ago

What do you see on the command line when you run npm install?

BostjanSkok commented 8 years ago

npm install npm WARN lifecycle micro-comb-ui@0.1.0~preinstall: cannot run in wd %s %s (wd=%s) micro-comb-ui@0.1.0 node tools/nodeVersionCheck.js /FrontEnd npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14 npm WARN optional Skipping failed optional dependency /browser-sync/chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

BostjanSkok commented 8 years ago

Now it starts watching files i ran $npm install babel -g

then it complained to uninstall babel so i did $npm uninstall babel $npm install babel-cli as requsted

than it complained about mocha and it would not install but $npm install mocha -g worked then esw was missing so i instaled eslint-watch now npm start -s seams to run

my current bin ls /FrontEnd/node_modules/.bin/ _mocha babel-external-helpers eslint npm-run-all run-p acorn babel-node esw rimraf run-s

Could i just install everything globaly since is a container ?

kwelch commented 8 years ago

If you run npm install from the project directory it will read the package.json and install all needed dependancies. Have you tried that?

BostjanSkok commented 8 years ago

yes running install returns my reviews comment just some

npm install npm WARN lifecycle micro-comb-ui@0.1.0~preinstall: cannot run in wd %s %s (wd=%s) micro-comb-ui@0.1.0 node tools/nodeVersionCheck.js /FrontEnd npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14 npm WARN optional Skipping failed optional dependency /browser-sync/chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

BostjanSkok commented 8 years ago

Should it try a fresh folder and do just npm install without the npm run setup

BostjanSkok commented 8 years ago

root@a3dc0e61be1d:/FrontEnd# npm install npm WARN deprecated tough-cookie@2.2.2: ReDoS vulnerability parsing Set-Cookie https://nodesecurity.io/advisories/130 npm WARN deprecated minimatch@2.0.10: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN deprecated minimatch@0.2.14: Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue npm WARN prefer global node-gyp@3.4.0 should be installed with -g

node-sass@3.8.0 install /FrontEnd/node_modules/node-sass node scripts/install.js

Binary downloaded and installed at /FrontEnd/node_modules/node-sass/vendor/linux-x64-48/binding.node

node-sass@3.8.0 postinstall /FrontEnd/node_modules/node-sass node scripts/build.js

npm WARN optional Skipping failed optional dependency /chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14 npm WARN optional Skipping failed optional dependency /browser-sync/chokidar/fsevents: npm WARN notsup Not compatible with your operating system or architecture: fsevents@1.0.14

coryhouse commented 8 years ago

That install looks good. You should be all set now. It appears the issue is you didn't run npm install initially.

When you type npm start you should see the example app now.

mycoin commented 8 years ago

There are a lot of problems !

npm install, lots of warns，Very slow（30min）

801M    node_modules/

Can you imagine？？ 801MB？

Dependences are not complete

npm WARN uninstall not installed in /Users/apple/Public/Lons/react-slingshot/node_modules: "babel"

npm start

Starting app in dev mode...
sh: esw: command not found
ERROR: "lint:watch" exited with 1.

... WTF

vjwilson commented 8 years ago

@mycoin ,

I'm seeing a much smaller node_modules directory:

    $ du -shc ./node_modules/
    174M  ./node_modules/
    174M  total

Try deleting the project's node_modules directory, make sure that your version of Node is at a version >= 3 (version >= 6 is even better), and upgrade that version of Node's npm to version >= 3.

Then, try running npm install again.

magestican commented 8 years ago

Ignoring this not working, what you can do is modify the file srcServer.js and pass the option quiet in true to suppress module loading information which to me is of no use :


middleware: [
      webpackDevMiddleware(bundler, {
        // Dev middleware can't access config, so we provide publicPath
        publicPath: config.output.publicPath,

        // pretty colored output
        stats: { colors: true },

        // Set to false to display a list of each file that is being bundled.
        noInfo: true,
        quiet:true
        // for other settings see
        // http://webpack.github.io/docs/webpack-dev-middleware.html
      }),
      // bundler should be the same as above
      webpackHotMiddleware(bundler),
      historyApiFallback()
    ]
  },

kwelch commented 7 years ago

This currently is no longer failing. Please submit a new issue if you see this in the future.

See @magestican's post ☝️ for controlling the webpack output.

Premjeet-Singh commented 7 years ago

Failed to run npm start -s OS: macOS sierra

clone this repo.
npm run setup
npm start -s

getting error: npm start -s Starting app in dev mode... No tests found In /Users/premsingh/Documents/Workspace/react-slingshot 50 files checked. testMatch: /tests//*.js?(x),*/?(.)(spec|test).js?(x) - 12 matches testPathIgnorePatterns: /node_modules/ - 50 matches Pattern: "--watch" - 0 matches

coryhouse commented 7 years ago

Thanks for reporting @Premjeet-Singh - I just committed a fix.

manideepcs024 commented 5 years ago

I am facing a issue with initial setup. git clone npm install npm start

after start message it fails react-slingshot@7.0.1 start: concurrently -k -r -s first "npm run test:watch" "npm run open:src" "npm run lint:watch"

please provide a solution. I have tried upgrading to latest version of node and also deleted node_modules and did npm install again but it fails.

konekoya commented 5 years ago

would you be able to provide a minimal repo that reproduces the error?

coryhouse / react-slingshot

npm start -s fails #231