step 1 : run any nuxt 3 project
step 2 : stop the system stop abruptly or shut down or close it
How often does it reproduce? Is there a required condition?
when the steps mentioned followed
What is the expected behavior? Why is that the expected behavior?
normal working of the project
What do you see instead?
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> npm install
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup [
npm WARN cleanup 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'
npm WARN cleanup }
npm WARN cleanup ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\vue-demi
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node -e "try{require('./scripts/postinstall.js')}catch(e){}"
npm ERR! 'node' is not recognized as an internal or external command,
npm ERR! operable program or batch file.
npm ERR! A complete log of this run can be found in: C:\Users\viswa\AppData\Local\npm-cache_logs\2024-02-29T15_08_05_358Z-debug-0.log
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> node -v
v20.11.1
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit>
Additional information
i tried every way possible i tried changing the nuxt 3 project its kept happening i tried uninstalling the node js and install it , used the wise programmer unisntaller done this process multiple times
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> npm install
npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1
npm WARN cleanup Failed to remove some directories [
npm WARN cleanup [
npm WARN cleanup 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules',
npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'] {
npm WARN cleanup errno: -4048,
npm WARN cleanup code: 'EPERM',
npm WARN cleanup syscall: 'rmdir',
npm WARN cleanup path: 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'
npm WARN cleanup }
npm WARN cleanup ]
npm WARN cleanup ]
npm ERR! code 1
npm ERR! path C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\vue-demi
npm ERR! command failed
npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node -e "try{require('./scripts/postinstall.js')}catch(e){}"
npm ERR! 'node' is not recognized as an internal or external command,
npm ERR! operable program or batch file.
npm ERR! A complete log of this run can be found in: C:\Users\viswa\AppData\Local\npm-cache_logs\2024-02-29T15_08_05_358Z-debug-0.log
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> node -v
v20.11.1
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit>
Version
v20.11.1
Platform
Microsoft Windows NT 10.0.22631.0 x64
Subsystem
No response
What steps will reproduce the bug?
step 1 : run any nuxt 3 project step 2 : stop the system stop abruptly or shut down or close it
How often does it reproduce? Is there a required condition?
when the steps mentioned followed
What is the expected behavior? Why is that the expected behavior?
normal working of the project
What do you see instead?
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> npm install npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules', npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'] { npm WARN cleanup errno: -4048, npm WARN cleanup code: 'EPERM', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 1 npm ERR! path C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\vue-demi npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node -e "try{require('./scripts/postinstall.js')}catch(e){}" npm ERR! 'node' is not recognized as an internal or external command, npm ERR! operable program or batch file.
npm ERR! A complete log of this run can be found in: C:\Users\viswa\AppData\Local\npm-cache_logs\2024-02-29T15_08_05_358Z-debug-0.log PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> node -v v20.11.1 PS C:\Users\viswa\Desktop\nuxt-proj\theluvit>
Additional information
i tried every way possible i tried changing the nuxt 3 project its kept happening i tried uninstalling the node js and install it , used the wise programmer unisntaller done this process multiple times
PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> npm install npm WARN deprecated popper.js@1.16.1: You can find the new Popper v2 at @popperjs/core, this package is dedicated to the legacy v1 npm WARN cleanup Failed to remove some directories [ npm WARN cleanup [ npm WARN cleanup 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules', npm WARN cleanup [Error: EPERM: operation not permitted, rmdir 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt'] { npm WARN cleanup errno: -4048, npm WARN cleanup code: 'EPERM', npm WARN cleanup syscall: 'rmdir', npm WARN cleanup path: 'C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\@nuxt' npm WARN cleanup } npm WARN cleanup ] npm WARN cleanup ] npm ERR! code 1 npm ERR! path C:\Users\viswa\Desktop\nuxt-proj\theluvit\node_modules\vue-demi npm ERR! command failed npm ERR! command C:\WINDOWS\system32\cmd.exe /d /s /c node -e "try{require('./scripts/postinstall.js')}catch(e){}" npm ERR! 'node' is not recognized as an internal or external command, npm ERR! operable program or batch file.
npm ERR! A complete log of this run can be found in: C:\Users\viswa\AppData\Local\npm-cache_logs\2024-02-29T15_08_05_358Z-debug-0.log PS C:\Users\viswa\Desktop\nuxt-proj\theluvit> node -v v20.11.1 PS C:\Users\viswa\Desktop\nuxt-proj\theluvit>