При npm start ошибка

Getting error while running comment «npm start» in windows 10.

showing error

Package.json

Packages.json

Log

• 0 info it worked if it ends with ok
• 1 verbose cli [ ‘C:Program Filesnodejsnode.exe’,
• 1 verbose cli ‘C:UsersvkaruthaAppDataRoamingnpmnode_modulesnpmbinnpm-cli.js’,
• 1 verbose cli ‘start’ ]
• 2 info using npm@4.2.0
• 3 info using node@v6.9.3
• 4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
• 5 info lifecycle hello-world@0.1.0~prestart: hello-world@0.1.0
• 6 silly lifecycle hello-world@0.1.0~prestart: no script for prestart, continuing
• 7 info lifecycle hello-world@0.1.0~start: hello-world@0.1.0
• 8 verbose lifecycle hello-world@0.1.0~start: unsafe-perm in lifecycle true
• 9 verbose lifecycle hello-world@0.1.0~start: PATH: C:UsersvkaruthaAppDataRoamingnpmnode_modulesnpmbinnode-gyp-bin;C:UsersvkaruthaDocumentsReacthello-worldnode_modules.bin;C:ProgramDataOracleJavajavapath;C:WINDOWSsystem32;C:WINDOWS;C:WINDOWSSystem32Wbem;C:WINDOWSSystem32WindowsPowerShellv1.0;C:Program Files (x86)WebExProductivity Tools;C:Program Files (x86)CiscoOSD-ShellApplications;C:Program FilesJavajdk1.8.0_101bin;C:Ciscosoftwareapache-maven-3.3.9bin;C:Program FilesGitcmd;C:Program Filesnodejs;C:Program FilesTortoiseSVNbin;C:Program Filesnodejsbin;C:Program Files (x86)SennheiserSoftphoneSDK;C:Program Files (x86)ssh communications securityssh Secure Shell;C:UsersvkaruthaAppDataRoamingnpm;C:Program Files (x86)Microsoft VS Codebin;C:Program Filesnodejsbin
• 10 verbose lifecycle hello-world@0.1.0~start: CWD: C:UsersvkaruthaDocumentsReacthello-world
• 11 silly lifecycle hello-world@0.1.0~start: Args: [ ‘/d /s /c’, ‘webpack-dev-server —hot’ ]
• 12 silly lifecycle hello-world@0.1.0~start: Returned: code: 4294967295 signal: null
• 13 info lifecycle hello-world@0.1.0~start: Failed to exec start script
• 14 verbose stack Error: hello-world@0.1.0 start: webpack-dev-server --hot
• 14 verbose stack Exit status 4294967295
• 14 verbose stack at EventEmitter. (C:UsersvkaruthaAppDataRoamingnpmnode_modulesnpmlibutilslifecycle.js:279:16)
• 14 verbose stack at emitTwo (events.js:106:13)
• 14 verbose stack at EventEmitter.emit (events.js:191:7)
• 14 verbose stack at ChildProcess. (C:UsersvkaruthaAppDataRoamingnpmnode_modulesnpmlibutilsspawn.js:40:14)
• 14 verbose stack at emitTwo (events.js:106:13)
• 14 verbose stack at ChildProcess.emit (events.js:191:7)
• 14 verbose stack at maybeClose (internal/child_process.js:877:16)
• 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
• 15 verbose pkgid hello-world@0.1.0
• 16 verbose cwd C:UsersvkaruthaDocumentsReacthello-world
• 17 error Windows_NT 10.0.10586
• 18 error argv «C:Program Filesnodejsnode.exe» «C:UsersvkaruthaAppDataRoamingnpmnode_modulesnpmbinnpm-cli.js» «start»
• 19 error node v6.9.3
• 20 error npm v4.2.0
• 21 error code ELIFECYCLE
• 22 error errno 4294967295
• 23 error hello-world@0.1.0 start: webpack-dev-server --hot
• 23 error Exit status 4294967295
• 24 error Failed at the hello-world@0.1.0 start script ‘webpack-dev-server —hot’.
• 24 error Make sure you have the latest version of node.js and npm installed.
• 24 error If you do, this is most likely a problem with the hello-world package,
• 24 error not with npm itself.
• 24 error Tell the author that this fails on your system:
• 24 error webpack-dev-server —hot
• 24 error You can get information on how to open an issue for this project with:
• 24 error npm bugs hello-world
• 24 error Or if that isn’t available, you can get their info via:
• 24 error npm owner ls hello-world
• 24 error There is likely additional logging output above.
• 25 verbose exit [ 4294967295, true ]

webpack.config.js

var config = {
   entry: './main.js',

   output: {
      path:'./',
      filename: 'index.js',
   },

   devServer: {
      inline: true,
      port: 8080
   },

   module: {
      loaders: [
         {
            test: /.jsx?$/,
            exclude: /node_modules/,
            loader: 'babel',

            query: {
               presets: ['es2015', 'react']
            }
         }
      ]
   }
}

asked Feb 15, 2017 at 9:19

There is a problem with your webpack.config.js file. You need to export the config object like this-

module.exports = {
   entry: './main.js',

   output: {
      path:'./',
      filename: 'index.js',
   },

   devServer: {
      inline: true,
      port: 8080
   },

   module: {
      loaders: [
         {
            test: /.jsx?$/,
            exclude: /node_modules/,
            loader: 'babel',

            query: {
               presets: ['es2015', 'react']
            }
         }
      ]
   }
}

answered Jan 19, 2021 at 7:17

I’m receiving this error when trying to debug my node application using the npm start command.

Error:

npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
npm ERR! node v0.12.7
npm ERR! npm  v2.11.3

npm ERR! missing script: start
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>npm ERR! Please include the following file with any support request:
npm ERR!     C:Usersandrmoll.NORTHAMERICADocumentsGitHubSVIChallengenpm-debug.log

From the debug file:

Error: missing script: start
       at run (C:Program Filesnodejsnode_modulesnpmlibrun-script.js:142:19)
       at C:Program Filesnodejsnode_modulesnpmlibrun-script.js:58:5
       at C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:345:5
       at checkBinReferences_ (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:309:45)
       at final (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:343:3)
       at then (C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:113:5)
       at C:Program Filesnodejsnode_modulesnpmnode_modulesread-package-jsonread-json.js:300:12
       at evalmachine.<anonymous>:334:14
       at C:Program Filesnodejsnode_modulesnpmnode_modulesgraceful-fsgraceful-fs.js:102:5
       at FSReqWrap.oncomplete (evalmachine.<anonymous>:95:15)

This error also happens if you added a second «scripts» key in the package.json file. If you just leave one «scripts» key in the package.json the error disappears.

answered Jun 29, 2021 at 6:42

You might have an old (global) installation of npm which causes the issue. As of 12/19, npm does not support global installations.

First, uninstall the package using:
npm uninstall -g create-react-app

Some osx/Linux users may need to also remove the old npm using:
rm -rf /usr/local/bin/create-react-app

This is now the only supported method for generating a project:
npx create-react-app my-app

Finally you can run:
npm start

answered May 16, 2020 at 18:05

answered Apr 6, 2021 at 9:38

Try with these steps :

npm rm -g create-react-app

npm install -g create-react-app

npx create-react-app my-app

Definitely this works!!

answered Jul 17, 2020 at 8:15

check package.json file having «scripts» property is there or not. if not update script property like this

{
  "name": "csvjson",
  "version": "1.0.0",
  "description": "upload csv to json and insert it into MongoDB for a single colletion",
  "scripts": {
    "start": "node csvjson.js"
  },
  "dependencies": {
    "csvjson": "^4.3.4",
    "fs": "^0.0.1-security",
    "mongodb": "^2.2.31"
  },
  "devDependencies": {},
  "repository": {
    "type": "git",
    "url": "git+https://github.com/giturl.git"
  },
  "keywords": [
    "csv",
    "json",
    "mongodb",
    "nodejs",
    "collection",
    "import",
    "export"
  ],
  "author": "karthikeyan.a",
  "license": "ISC",
  "bugs": {
    "url": "https://github.com/homepage/issues"
  },
  "homepage": "https://github.com/homepage#readme"
}

answered Sep 1, 2017 at 11:03

If you are using babelify and watchify, go to:

package.json

and add this in «scripts»:

"scripts": {
    "start": "watchify the-path-to-your-source-jsx-file -v -t [ babelify --presets [ react ] ] -o the-path-to-your-output-js-file"
}

An example would be:

"scripts": {
    "start": "watchify src/main.jsx -v -t [ babelify --presets [ react ] ] -o public/js/main.js"
}

Thanks to Mark Price from DevSlopes

Installing create-react-app globally is now discouraged. Instead uninstall globally installed create-react-app package by doing: npm uninstall -g create-react-app (you may have to manually delete package folder if this command didn’t work for you. Some users have reported they had to delete folders manually)

Then you can run npx create-react-app my-app to create react app again.

ref: https://github.com/facebook/create-react-app/issues/8086

answered Jan 23, 2020 at 19:40

answered May 31, 2021 at 21:53

Make sure the PORTS ARE ON

var app = express();
app.set('port', (process.env.PORT || 5000));

BLAL BLA BLA AND AT THE END YOU HAVE THIS

app.listen(app.get('port'), function() {
    console.log("Node app is running at localhost:" + app.get('port'))
});

Still a newbee in node js but this caused more of this.

answered Mar 1, 2017 at 12:35

Take a look at your client/package.json. You have to have these scripts

"scripts": {
  "start": "react-scripts start",
  "build": "react-scripts build",
  "test": "react-scripts test --env=jsdom",
  "eject": "react-scripts eject"
}

answered Apr 8, 2020 at 10:05

I got this error because I wasn’t in the right directory in terminal.

App with the scripts was in folder B. Folder B was in folder A. I open folder A in vscode and enter «npm run start» into the built in terminal and got the error. try «cd folder B», opening folder B in the ide, or organizing your stuff better than I did in the first place.

answered Jan 14, 2021 at 0:08

answered Aug 4, 2022 at 7:49

answered Sep 13, 2022 at 7:17

There are more answers regarding to scripts. Here is my 2 cents. If you having the same issue just after creating the react app or just started the work in the day, in most case this is what happened. You may not got inside of the created project.

Suppose you created a react app as my-app. then you have to go inside of the app before you run nmp start command.

1. cd my-app

2. npm start

It will work fine.

answered Nov 1, 2022 at 12:12

Check if you have nodemon installed, if you do, run the script using nodemon the start script in your package.json Example nodemon start

Also, do remember to change directory into the exact folder where you server was installed. You will get this error if you run the npm start command from a parent folder of your project.

That was how I got this error.

answered Feb 12 at 9:04