"npm install" command is returning errors below and "npm start" is not opening my development server

[Masangwi-Tatenda]

PS C:\Users\User\Desktop\Personal Portfolio\frontend_react> npm install npm WARN deprecated stable@0.1.8: 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 source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated flatten@1.0.3: flatten is deprecated in favor of utility frameworks such as lodash. npm WARN deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see request/request#3142 npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated w3c-hr-time@1.0.2: Use your platform's native performance.now() and performance.timeOrigin. npm WARN deprecated left-pad@1.3.0: use String.prototype.padStart() npm WARN deprecated sane@4.1.0: some dependency vulnerabilities fixed, support for node < 10 dropped, and newer ECMAScript syntax/features added npm WARN deprecated eslint-loader@3.0.3: This loader has been deprecated. Please use eslint-webpack-plugin npm WARN deprecated html-webpack-plugin@4.0.0-beta.11: please switch to a stable version npm WARN deprecated babel-eslint@10.1.0: babel-eslint is now @babel/eslint-parser. This package will no longer receive updates. 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 WARN deprecated request@2.88.2: request has been deprecated, see request/request#3142 npm WARN deprecated svgo@1.3.2: This SVGO version is no longer supported. Upgrade to v2.x.x. npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup 'C:\Users\User\Desktop\Personal Portfolio\frontend_react\node_modules\.which-collection-T49Xwuxy', npm WARN cleanup [Error: EBUSY: resource busy or locked, rmdir 'C:\Users\User\Desktop\Personal Portfolio\frontend_react\node_modules.which-collection-T49Xwuxy'] { npm WARN cleanup errno: -4082, npm WARN cleanup code: 'EBUSY', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: 'C:\Users\User\Desktop\Personal Portfolio\frontend_react\node_modules\.which-collection-T49Xwuxy' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] added 428 packages, changed 646 packages, and audited 1862 packages in 13m 140 packages are looking for funding run npm fund for details 119 vulnerabilities (1 low, 97 moderate, 17 high, 4 critical) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run npm audit for details.

[aros0918]

hello,
I will give you 4 steps

1. Update the deprecated packages: Review the warning messages and identify the packages that are deprecated. Check the provided links or the package documentation to find the recommended alternatives. Update the relevant packages to their latest versions or replace them with the suggested alternatives.

2. Resolve vulnerabilities: Run npm audit to get detailed information about the vulnerabilities. Based on the severity level, you can choose to address the vulnerabilities by running npm audit fix or npm audit fix --force to automatically fix the issues. However, it's recommended to review the changes carefully before applying them.

3. Remove unnecessary packages: If there are any unused or unnecessary packages, consider removing them from your project to reduce the number of vulnerabilities and potential issues.

4. Follow best practices: Stay up to date with the latest releases and security recommendations for your project's dependencies. Regularly check for updates, security patches, and community support to ensure the stability and security of your project.

if you following these 4 steps, you can get achievement. thank you