Bug: Npm Start not working in react project using either Vite or C-R-A

[Perspective2077]

React version: 19.0.0

Steps To Reproduce

1. i donno it's just in my system
2. i donno if this is right place also i don't have stack overflow nor you guys operate a discord server..

Link to code example:

The current Error it is showing

PS F:\projects\Simple\bonvoyage> npm start

[email protected] start
react-scripts start

PS F:\projects\Simple\bonvoyage>

It is not showing the error just skipping everything

The Error when installing node_modules or creating a new react project

npm warn deprecated [email protected]: Use your platform's native performance.now() and performance.timeOrigin.
npm warn deprecated [email protected]: [email protected]
npm warn deprecated [email protected]: It is not compatible with newer versions of GA starting with v4, as long as you are using GAv3 it should be ok, but the package is not longer being maintained
npm warn deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
npm warn deprecated [email protected]: Please use @jridgewell/sourcemap-codec instead
npm warn deprecated [email protected]: Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility
npm warn deprecated [email protected]: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm warn deprecated [email protected]: Rimraf versions prior to v4 are no longer supported
npm warn deprecated [email protected]: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other.
npm warn deprecated
npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp)
npm warn deprecated [email protected]: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.
npm warn deprecated [email protected]: Glob versions prior to v9 are no longer supported
npm warn deprecated [email protected]: Use your platform's native DOMException instead
npm warn deprecated [email protected]: Use your platform's native atob() and btoa() methods instead
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/object-schema instead
npm warn deprecated @humanwhocodes/[email protected]: Use @eslint/config-array instead
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.
npm warn deprecated @babel/[email protected]: This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.
npm warn deprecated [email protected]: This version is no longer supported. Please see https://eslint.org/version-support for other options.
npm warn cleanup Failed to remove some directories [
npm warn cleanup [
npm warn cleanup '\\?\F:\projects\trail\node_modules\jest-watch-typeahead\node_modules\jest-watcher',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'F:\projects\trail\node_modules\jest-watch-typeahead\node_modules\jest-watcher'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'F:\projects\trail\node_modules\jest-watch-typeahead\node_modules\jest-watcher'
npm warn cleanup }
npm warn cleanup ],
npm warn cleanup [
npm warn cleanup '\\?\F:\projects\trail\node_modules',
npm warn cleanup [Error: EPERM: operation not permitted, rmdir 'F:\projects\trail\node_modules\clean-css'] {
npm warn cleanup errno: -4048,
npm warn cleanup code: 'EPERM',
npm warn cleanup syscall: 'rmdir',
npm warn cleanup path: 'F:\projects\trail\node_modules\clean-css'
npm warn cleanup }
npm warn cleanup ]
npm warn cleanup ]
npm error code ERR_INVALID_ARG_TYPE
npm error The "file" argument must be of type string. Received undefined
npm error A complete log of this run can be found in: C:\Users\user\AppData\Local\npm-cache_logs\2025-03-01T12_29_06_935Z-debug-0.log
PS F:\projects\trail>

The expected behavior

I mean should install and start the project...?

[VetSoftKeith]

I created and built new projects using the instructions for each Vite and CRA (CRA is officially deprecated, in case you missed that announcement). And both built and ran fine for me out of the box.

But looking at your stacktrace, you have several issues going on; outdated dependencies, file system permission issues. Might wanna start by looking into fixing those things. As for React, installs and builds fine on my machine using node 22 regardless of the framework used to create it.