Ошибка npm run dev - Ремонт и установка крупной бытовой техники

I have next errors output running npm command for my laravel 5.6 with bootstrap project:

$ npm run dev

> @ dev /mnt/_work_sdb8/wwwroot/lar/B4test
> npm run development


> @ development /mnt/_work_sdb8/wwwroot/lar/B4test
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js

sh: 1: cross-env: not found
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! spawn ENOENT
npm ERR! 
npm ERR! Failed at the @ development script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/serge/.npm/_logs/2018-04-25T10_54_37_776Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: `npm run development`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/serge/.npm/_logs/2018-04-25T10_54_37_794Z-debug.log

File /home/serge/.npm/_logs/2018-04-25T10_54_37_776Z-debug.log has:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'development' ]
2 info using npm@6.0.0
3 info using node@v9.11.1
4 verbose run-script [ 'predevelopment', 'development', 'postdevelopment' ]
5 info lifecycle @~predevelopment: @
6 info lifecycle @~development: @
7 verbose lifecycle @~development: unsafe-perm in lifecycle true
8 verbose lifecycle @~development: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/_work_sdb8/wwwroot/lar/B4test/node_modules/.bin:/usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/mnt/_work_sdb8/wwwroot/lar/B4test/node_modules/.bin:/home/serge/.composer/vendor/bin:/home/serge/.composer/vendor/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin:~/.composer/vendor/bin
9 verbose lifecycle @~development: CWD: /mnt/_work_sdb8/wwwroot/lar/B4test
10 silly lifecycle @~development: Args: [ '-c',
10 silly lifecycle   'cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js' ]
11 info lifecycle @~development: Failed to exec development script
12 verbose stack Error: @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
12 verbose stack spawn ENOENT
12 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:48:18)
12 verbose stack     at ChildProcess.emit (events.js:180:13)
12 verbose stack     at maybeClose (internal/child_process.js:936:16)
12 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:220:5)
13 verbose pkgid @
14 verbose cwd /mnt/_work_sdb8/wwwroot/lar/B4test
15 verbose Linux 4.13.0-38-generic
16 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "development"
17 verbose node v9.11.1
18 verbose npm  v6.0.0
19 error file sh
20 error code ELIFECYCLE
21 error errno ENOENT
22 error syscall spawn
23 error @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
23 error spawn ENOENT
24 error Failed at the @ development script.
24 error This is probably not a problem with npm. There is likely additional logging output above.
25 verbose exit [ 1, true ]

In composer.json :

{
    "name": "laravel/laravel",
    "description": "The Laravel Framework.",
    "keywords": ["framework", "laravel"],
    "license": "MIT",
    "type": "project",
    "require": {
        "php": "^7.1.3",
        "fideloper/proxy": "^4.0",
        "laravel/framework": "5.6.*",
        "components/highlightjs": "^9.12",
        "doctrine/dbal": "^2.6",
        "intervention/image": "^2.4",
        "laracasts/utilities": "^3.0",
        "laravel/tinker": "~1.0",
        "nwidart/laravel-modules": "^3.0",
        "pusher/pusher-php-server": "^3.0",
        "spatie/laravel-backup": "^5.1",
        "wboyz/laravel-enum": "^0.2.1"
    },
    "require-dev": {
        "filp/whoops": "^2.0",
        "fzaninotto/faker": "^1.7",
        "mockery/mockery": "^1.0",
        "nunomaduro/collision": "^2.0",
        "phpunit/phpunit": "^7.0",
        "barryvdh/laravel-debugbar": "^3.1",
        "laravel/dusk": "~3.0"
    },
    "autoload": {
        "classmap": [
            "database/seeds",
            "database/factories"
        ],
        "psr-4": {
            "App\": "app/",
            "Modules\": "Modules/"
        }
    },
    "autoload-dev": {
        "psr-4": {
            "Tests\": "tests/"
        }
    },
    "extra": {
        "laravel": {
            "dont-discover": [
            ]
        }
    },
    "scripts": {
        "post-root-package-install": [
            "@php -r "file_exists('.env') || copy('.env.example', '.env');""
        ],
        "post-create-project-cmd": [
            "@php artisan key:generate"
        ],
        "post-autoload-dump": [
            "Illuminate\Foundation\ComposerScripts::postAutoloadDump",
            "@php artisan package:discover"
        ]
    },
    "config": {
        "preferred-install": "dist",
        "sort-packages": true,
        "optimize-autoloader": true
    },
    "minimum-stability": "dev",
    "prefer-stable": true
}

In package.json :

{
    "private": true,
    "scripts": {
        "dev": "npm run development",
        "development": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",
        "watch": "npm run development -- --watch",
        "watch-poll": "npm run watch -- --watch-poll",
        "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",
        "prod": "npm run production",
        "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --no-progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"
    },
    "devDependencies": {
        "axios": "^0.18",
        "bootstrap": "^4.0.0",
        "popper.js": "^1.12",
        "cross-env": "^5.1",
        "jquery": "^3.2",
        "laravel-mix": "^2.0",
        "lodash": "^4.17.4",
        "vue": "^2.5.7",
        "vue-template-compiler": "^2.5.16",
        "vue2-collapse": "^1.0.11"
    },
    "dependencies": {
        "element-ui": "^2.3.6",
        "font-awesome": "^4.7.0",
        "fullcalendar": "^3.9.0",
        "highlight.js": "^9.12.0",
        "laravel-echo": "^1.3.5",
        "marked": "^0.3.19",
        "pusher-js": "^4.2.2",
        "v-toaster": "^1.0.3",
        "vee-validate": "^2.0.6",
        "vee-validate-laravel": "^1.0.1",
        "vue-bootstrap-datetimepicker": "^4.1.3",
        "vue-chat-scroll": "^1.2.1",
        "vue-fullcalendar": "^1.0.9",
        "vue-js-popover": "^1.1.7",
        "vue-moment": "^3.2.0",
        "vue-mouse-menu": "^1.1.0",
        "vue-nl2br": "0.0.5",
        "vue-notify-me": "^1.1.0",
        "vue-popperjs": "^1.2.6",
        "vue-router": "^3.0.1",
        "vue-select": "^2.4.0",
        "vue-simple-calendar": "^2.2.0",
        "vue-timeago": "^3.4.4",
        "vuejs-datepicker": "^0.9.29"
    }
}

Can you give a hint what could raize an error and how to fix it ?

Some error in config files or what?

Thank you very much!

Источник

Guys can you please help me on this I have trouble run npm run dev for my Laravel Mix. I followed links below but still error exist. Do i have a problem on my OS? I tried to remove node_modules, run npm install —global cross-env. and run NPM install again.

‘cross-env’ is not recognized as an internal or external command,

https://github.com/JeffreyWay/laravel-mix/issues/478

The error I always get when I ran npm run dev :

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ development script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/baloghdominik/.npm/_logs/2020-02-26T17_05_54_290Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ dev: `npm run development`
npm ERR! Exit status 1
npm ERR! 
npm ERR! Failed at the @ dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/baloghdominik/.npm/_logs/2020-02-26T17_05_54_315Z-debug.log

miken32

41.6k16 gold badges108 silver badges154 bronze badges

asked Feb 26, 2020 at 17:14

Dominik BaloghDominik Balogh

3051 gold badge3 silver badges12 bronze badges

First run

npm install cross-env

npm install

Then run

npm run dev

answered Feb 26, 2020 at 17:23

VIKAS KATARIYAVIKAS KATARIYA

5,8393 gold badges16 silver badges34 bronze badges

Simple steps :

npm cache clear —force
delete node_modules and package-lock.json
npm install
npm run dev

answered Apr 9, 2021 at 14:47

rm -rf node_modules
rm package-lock.json yarn.lock
npm cache clear --force
npm install

Basically delete the node_modules folder and package-lock.json file , clear cache and do an npm install. Worked for me.

dbc

103k20 gold badges222 silver badges333 bronze badges

answered Apr 8, 2021 at 18:10

In my case I had old version of node.js
so I just installed version I need:

sudo npm install n -g

sudo n stable

Or can try use latest:

sudo n latest

answered Apr 23, 2021 at 0:25

If u using nvm, u need use version for project. Commands helped for me:

Use default version node: nvm use system
Remove node_modules rm -rf node_modules and rm -f package-lock.json
Clear cache npm cache clear --force
Finished command npm i

answered Dec 25, 2022 at 12:56

Источник

npm install —save-dev webpack webpack-cli webpack-dev-server

увы все равно выдает ошибку( сделала по новой вот весь мой путь в терминале((( на сколько эта ошибка критична в дальнейшей работе?

Женя@DESKTOP-2O5UR37 MINGW64 ~/Desktop/webpacktest
$ npm init
This utility will walk you through creating a package.json file.
It only covers the most common items, and tries to guess sensible defaults.

See npm help init for definitive documentation on these fields
and exactly what they do.

Use npm install <pkg> afterwards to install a package and
save it as a dependency in the package.json file.

Press ^C at any time to quit.
package name: (webpacktest)
version: (1.0.0)
description: my template
entry point: (index.js)
test command: test
git repository:
keywords:
author: Markova
license: (ISC) MIT
About to write to C:UsersЖеняDesktopwebpacktestpackage.json:

{
«name»: «webpacktest»,
«version»: «1.0.0»,
«description»: «my template»,
«main»: «index.js»,
«scripts»: {
«test»: «test»
},
«author»: «Markova»,
«license»: «MIT»
}

Is this OK? (yes)

Женя@DESKTOP-2O5UR37 MINGW64 ~/Desktop/webpacktest
$ npm install —save-dev webpack webpack-cli webpack-dev-server
npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is
known to be problematic. See https://v8.dev/blog/math-random for details.
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_moduleschokidarnode_modulesfsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»win32″,»arch»:»x64″})
npm WARN webpacktest@1.0.0 No repository field.

webpack-dev-server@3.11.2
webpack-cli@4.7.0
webpack@5.38.1
added 493 packages from 321 contributors and audited 494 packages in 31.692s

27 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

Женя@DESKTOP-2O5UR37 MINGW64 ~/Desktop/webpacktest
$ npm install path
npm WARN webpacktest@1.0.0 No repository field.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.13 (node_modulesfsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {«os»:»darwin»,»arch»:»any»} (current: {«os»:»win32″,»arch»:»x64″})

path@0.12.7
added 4 packages from 2 contributors and audited 498 packages in 3.954s

27 packages are looking for funding
run npm fund for details

found 0 vulnerabilities

Женя@DESKTOP-2O5UR37 MINGW64 ~/Desktop/webpacktest
$ npm run dev

webpacktest@1.0.0 dev C:UsersЖеняDesktopwebpacktest
webpack-dev-server —open —mode development

internal/modules/cjs/loader.js:888
throw err;
^

Error: Cannot find module ‘webpack-cli/bin/config-yargs’
Require stack:

C:UsersЖеняDesktopwebpacktestnode_moduleswebpack-dev-serverbinwebpack-dev-server.js
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:885:15)
at Function.Module._load (internal/modules/cjs/loader.js:730:27)
at Module.require (internal/modules/cjs/loader.js:957:19)
at require (internal/modules/cjs/helpers.js:88:18)
at Object. (C:UsersЖеняDesktopwebpacktestnode_moduleswebpack-dev-serverbinwebpack-dev-server.js:65:1)
at Module._compile (internal/modules/cjs/loader.js:1068:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:1097:10)
at Module.load (internal/modules/cjs/loader.js:933:32)
at Function.Module._load (internal/modules/cjs/loader.js:774:14)
at Function.executeUserEntryPoint [as runMain] (internal/modules/run_main.js:72:12) {
code: ‘MODULE_NOT_FOUND’,
requireStack: [
‘C:UsersЖеняDesktopwebpacktestnode_moduleswebpack-dev-serverbinwebpack-dev-server.js’
]
}
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! webpacktest@1.0.0 dev: webpack-dev-server --open --mode development
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the webpacktest@1.0.0 dev script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:UsersЖеняAppDataRoamingnpm-cache_logs2021-05-29T10_36_52_294Z-debug.log

Источник

При выполнение команды «npm run dev» возникает следующая проблема:

> @ dev c:ProgramsOpenServerOSPaneldomainslocalhostkorona-it                             
> npm run development                                                                          
                                                                                               
                                                                                               
> @ development c:ProgramsOpenServerOSPaneldomainslocalhostkorona-it                     
> cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules 
                                                                                               
98% after emitting SizeLimitsPlugin                                                            
                                                                                               
 ERROR  Failed to compile with 2 errors                                                        
 error  in ./resources/sass/app.scss                                                           
                                                                                               
Module build failed (from ./node_modules/css-loader/index.js):                                 
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):           
ValidationError: Invalid options object. Sass Loader has been initialized using an options obje
 - options has an unknown property 'outputStyle'. These properties are valid:                  
   object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? }        
    at validate (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesschema
    at Object.loader (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduless
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduleswebpacklibNorm
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at runSyncOrAsync (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modules
    at iterateNormalLoaders (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_mo
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesenhanced-resolve
    at processTicksAndRejections (internal/process/task_queues.js:79:11)                       
                                                                                               
 error  in ./resources/sass/app.scss                                                           
                                                                                               
Module build failed (from ./node_modules/sass-loader/dist/cjs.js):                             
ValidationError: Invalid options object. Sass Loader has been initialized using an options obje
 - options has an unknown property 'outputStyle'. These properties are valid:                  
   object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? }        
    at validate (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesschema
    at Object.loader (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduless
                                                                                               
 @ ./resources/sass/app.scss 2:14-253                                                          
                                                                                               
     Asset      Size   Chunks             Chunk Names                                          
/js/app.js  1.41 MiB  /js/app  [emitted]  /js/app                                              
                                                                                               
ERROR in ./resources/sass/app.scss                                                             
Module build failed (from ./node_modules/css-loader/index.js):                                 
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):           
ValidationError: Invalid options object. Sass Loader has been initialized using an options obje
 - options has an unknown property 'outputStyle'. These properties are valid:                  
   object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? }        
    at validate (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesschema
    at Object.loader (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduless
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduleswebpacklibNorm
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at runSyncOrAsync (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modules
    at iterateNormalLoaders (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_mo
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesloader-runnerli
    at c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesenhanced-resolve
    at processTicksAndRejections (internal/process/task_queues.js:79:11)                       
 @ ./resources/sass/app.scss                                                                   
                                                                                               
ERROR in ./resources/sass/app.scss (./node_modules/css-loader??ref--5-2!./node_modules/postcss-
Module build failed (from ./node_modules/sass-loader/dist/cjs.js):                             
ValidationError: Invalid options object. Sass Loader has been initialized using an options obje
 - options has an unknown property 'outputStyle'. These properties are valid:                  
   object { implementation?, sassOptions?, prependData?, sourceMap?, webpackImporter? }        
    at validate (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_modulesschema
    at Object.loader (c:ProgramsOpenServerOSPaneldomainslocalhostkorona-itnode_moduless
 @ ./resources/sass/app.scss 2:14-253                                                          
npm ERR! code ELIFECYCLE                                                                       
npm ERR! errno 2                                                                               
npm ERR! @ development: `cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --p
npm ERR! Exit status 2                                                                         
npm ERR!                                                                                       
npm ERR! Failed at the @ development script.                                                   
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
                                                                                               
npm ERR! A complete log of this run can be found in:                                           
npm ERR!     C:UsersACERAppDataRoamingnpm-cache_logs2021-01-29T14_55_02_953Z-debug.log  
npm ERR! code ELIFECYCLE                                                                       
npm ERR! errno 2                                                                               
npm ERR! @ dev: `npm run development`                                                          
npm ERR! Exit status 2                                                                         
npm ERR!                                                                                       
npm ERR! Failed at the @ dev script.                                                           
npm ERR! This is probably not a problem with npm. There is likely additional logging output abo
                                                                                               
npm ERR! A complete log of this run can be found in:                                           
npm ERR!     C:UsersACERAppDataRoamingnpm-cache_logs2021-01-29T14_55_03_001Z-debug.log

Не как не могу понять, что именно не так(

Источник

When developing Node.js applications, the npm run script is an essential tool for running various tasks and scripts in your project. However, sometimes when you run the command «npm run dev» or any other script, you may encounter an error message that says «missing script: dev» or «script ‘dev’ not found.» This error is typically caused by the lack of a script named «dev» in the «scripts» section of your package.json file. In this article, we will discuss several methods to resolve this issue and successfully run the desired script.

Method 1: Specifying the script in package.json

To resolve the npm run dev missing script issue in Node.js, you can specify the script in the package.json file. Here are the steps to do it:

Open your project’s package.json file.
Locate the scripts section.
Add a new script called dev with the command you want to run. For example:

"scripts": {
  "dev": "nodemon server.js"
}

In this example, we’re using nodemon to watch for changes in the server.js file and automatically restart the server when changes are detected.

Save the package.json file.
Open your terminal and navigate to your project’s root directory.
Run the npm run dev command.

This will execute the dev script specified in the package.json file. If everything is set up correctly, your Node.js application should start running.

Here’s another example of a dev script that uses webpack to build a project:

"scripts": {
  "dev": "webpack-dev-server --mode development --open"
}

In this example, we’re using webpack-dev-server to start a development server and open the project in a new browser window.

By specifying the dev script in the package.json file, you can easily run your Node.js application without having to remember the full command each time.

Method 2: Creating a custom script in package.json

To resolve the «npm run dev missing script» issue in Node.js, you can create a custom script in your package.json file. Here are the steps:

Open your package.json file.
Under the «scripts» section, add a new script with the name «dev» and the command you want to run. For example:

"scripts": {
  "start": "node index.js",
  "dev": "nodemon index.js"
},

Save the package.json file.
In your terminal, run the command «npm run dev» to start your development server.

In the above example, we have created a custom script called «dev» that uses the nodemon package to automatically restart the server when changes are made to the code.

You can customize the script to your needs by changing the command to whatever you want to run for your development environment.

Remember to always save your changes in the package.json file before running the script.

Method 3: Checking for typos in the script name

To resolve the «npm run dev missing script» issue in Node.js, you can start by checking for typos in the script name. Here are the steps you can follow:

Open your terminal and navigate to your project directory.
Run the command npm run to see a list of available scripts.
Check if the script you are trying to run is listed. If not, you may have misspelled the script name in your package.json file.
Open your package.json file and check the scripts section.
Make sure the script name you are trying to run is spelled correctly and matches the name in the scripts section.
If you have made changes to the package.json file, make sure to save the file before running the script again.

Here is an example package.json file with a dev script:

{
  "name": "my-project",
  "version": "1.0.0",
  "description": "My project description",
  "scripts": {
    "dev": "nodemon app.js"
  },
  "dependencies": {
    "nodemon": "^2.0.7"
  }
}

In this example, the dev script runs the nodemon package with the app.js file. To run this script, you would use the command npm run dev.

If you still encounter the «npm run dev missing script» issue after checking for typos, you may need to reinstall the package dependencies or check for any other errors in your code.

Method 4: Installing and Updating npm and Node.js

To resolve the «npm run dev missing script issues» in Node.js, you can follow these steps to install and update npm and Node.js:

Install Node.js:

sudo apt-get install nodejs

Install npm:

Update npm:

Update Node.js:

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

Verify the installation and versions:

Once you have done these steps, you can try running the «npm run dev» command again and it should work without any issues.

Note: If you are still facing issues, you can try deleting the «node_modules» folder and the «package-lock.json» file, and then running «npm install» to reinstall the dependencies.

That’s it! By following these steps, you should be able to resolve the «npm run dev missing script issues» in Node.js.

Источник