npm ERR! Missing script: "dev"

[felyan]

Hi! I'm trying to create a React project with Vite. The project folder is ready, npm installed, the package.json file is fine, and it includes the necessary lines, such as:
"scripts": {
"dev": "vite",
"build": "vite build",
"lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0",
"preview": "vite preview"
}
Now, I'm facing the issue that when I run the npm run dev command, I get the following error message:
npm ERR! Missing script: "dev"
npm ERR!
npm ERR! To see a list of scripts, run: npm ERR! npm run
After running npm run, I get this:
Lifecycle scripts included in [email protected]: test echo "Error: no test specified" && exit 1
What should I do to be able to open my project in the browser?

[leeringrose]

@felyan I would recommend you remove your node_modules folder from your project and also remove package-lock.json and re-run npm install --save-dev.

[felyan]

Sorry, I messed this up. Restored, and running the npm run dev command

[leeringrose]

@felyan Have you installed all the npm modules required after recovering your package.json file?
Could I look in your package.json file? What do the script options look like?

[felyan]

[felyan]

I haven't manually installed anything into the npm modules; it contains what was installed automatically.

[felyan]

Thank you very much for your response. The necessary scripts are in place, and I've already gone through the steps you mentioned before, unfortunately without success. The strange thing about all this is that about a month ago, I was working on a React project, and everything was working smoothly back then. Since then, my computer hasn't been reinstalled or undergone any similar interventions.

[leeringrose]

If you fully followed this guide up to facing this issue. https://vitejs.dev/guide
I would recommend you reinstall your node and check all stuff after re-installation. I expected after the re-installation of your vite globally, it would work fine.

[felyan]

Thank you for the help, it works! (Strange, because I've reinstalled it several times and ran into the same error. Magic:) )

[hectrhcc]

I'm having the same issue but in my case, after running npm install, it is not creating the node_modules folder nor the package-lock.json file.

[hectrhcc]

Okay, my problem was actually quite simple to resolve, because I was making a mistake. In my case I was entering the command npm create vite@latest and npm install without first entering the vite-project folder, where I should have run npm install and then npm run dev.

[RaxCode0101]

oh my godsh, thank you man, i forgot to entering the vite-project.

[shivam7147]

Thanks a lot i was struggling from this for 2 days but u saved the 3rd one.

[RemoSande]

I am having the same issue with Vite and it broke my project. Some things I have done:

• reinstalled node.js
• double checking the directory
• reinstalling packages, removing the package lock, deleting and reinstalling node_modules.

Whatever I do I get the following errors when trying npm run dev:

npm ERR! Missing script: "dev"
npm ERR! 
npm ERR! To see a list of scripts, run:
npm ERR!   npm run

npm ERR! A complete log of this run can be found in

Help is appreciated!

[gwenfisch]

Did you get the issue after upgrading node to v20.11.1 ?

[RemoSande]

I doubt it but it is possible.. In the meantime I will re-install, start a fresh project and copy paste my project.

[RemoSande]

oke so I cannot even create a new vite app ouch. I'm locked out and lost allot of time already. Any help is appreciated!
npm ERR! code 127 npm ERR! path C:\SpaceMonk\CodeCave\React\class01 npm ERR! command failed npm ERR! command bash -c create-vite

When running npm cache clean --force :
`C:\Windows\System32>npm cache clean --force
npm WARN using --force Recommended protections disabled.

C:\Windows\System32>npm install -g vite
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup [
npm WARN cleanup 'C:\Users\aidoj\AppData\Roaming\npm\node_modules\vite',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\aidoj\AppData\Roaming\npm\node_modules\vite\node_modules\rollup\dist\shared'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\aidoj\AppData\Roaming\npm\node_modules\vite\node_modules\rollup\dist\shared'
npm WARN cleanup }
npm WARN cleanup ]
npm WARN cleanup ]
npm ERR! code 127
npm ERR! path C:\Users\aidoj\AppData\Roaming\npm\node_modules\vite\node_modules\esbuild
npm ERR! command failed
npm ERR! command bash -c node install.js
npm ERR! /mnt/c/Users/aidoj/AppData/Roaming/npm/node_modules/node/bin/node: 1: This: not found

npm ERR! A complete log of this run can be found in: C:\Users\aidoj\AppData\Local\npm-cache_logs\2024-03-08T13_09_03_950Z-debug-0.log`

[RemoSande]

Npm run dev returns:
`C:\Users\aidoj\OneDrive\Desktop\react2>npm run dev
npm ERR! Missing script: "dev"
npm ERR!
npm ERR! To see a list of scripts, run:
npm ERR! npm run

npm ERR! A complete log of this run can be found in: C:\Users\aidoj\AppData\Local\npm-cache_logs\2024-03-08T13_47_41_707Z-debug-0.log

C:\Users\aidoj\OneDrive\Desktop\react2>`

while my JSON seems correct. I am baffled.

{ "name": "vite-project", "private": true, "version": "0.0.0", "type": "module", "scripts": { "dev": "vite", "build": "vite build", "lint": "eslint . --ext js,jsx --report-unused-disable-directives --max-warnings 0", "preview": "vite preview" }, "dependencies": { "react": "^18.2.0", "react-dom": "^18.2.0" }, "devDependencies": { "@types/react": "^18.2.56", "@types/react-dom": "^18.2.19", "@vitejs/plugin-react": "^4.2.1", "eslint": "^8.56.0", "eslint-plugin-react": "^7.33.2", "eslint-plugin-react-hooks": "^4.6.0", "eslint-plugin-react-refresh": "^0.4.5", "vite": "^5.1.4" } }

[RemoSande]

setting up a new project finally worked for me ! unsure why I have these problems with existing projects.

[sonu895]

This comment was marked as off-topic.

how would you get the solution because i m suffering from the same

[mutyabaronald]

how do l solve such an error

[RemoSande]

usually these problem arise from being in the wrong directory when calling npm.

[Farial-mahmod]

Sometimes it happens due to being in the wrong directory. Ensuring to run "npm install" after modifying the package.json may help to resolve it.

[swssuraj]