-
Notifications
You must be signed in to change notification settings - Fork 4.9k
Description
Win10 x64 command just breaks in process. REQUIRED ADMIN priveledges to run.
ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\Program Files\nodejs\node_modules.staging
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'
npm ERR! [OperationalError: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'] {
npm ERR! cause: [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'] {
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\Program Files\nodejs\node_modules\.staging'
npm ERR! },
npm ERR! errno: -4048,
npm ERR! code: 'EPERM',
npm ERR! syscall: 'mkdir',
npm ERR! path: 'C:\Program Files\nodejs\node_modules\.staging',
npm ERR! parent: '@babel/core'
npm ERR! }
npm ERR!
npm ERR! The operation was rejected by your operating system.
npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
npm ERR! or that you lack permissions to access it.
npm ERR!
npm ERR! If you believe this might be a permissions issue, please double-check the
npm ERR! permissions of the file and its containing directories, or try running
npm ERR! the command again as root/Administrator.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\User\AppData\Roaming\npm-cache_logs\2021-02-03T08_07_20_266Z-debug.log
//==============================================================================
Records from log:
16535 verbose unlock done using C:\Users\User\AppData\Roaming\npm-cache_locks\staging-dfd8fbf9c1feea0f.lock for C:\Program Files\nodejs\node_modules.staging
16536 timing stage:rollbackFailedOptional Completed in 1ms
16537 timing stage:runTopLevelLifecycles Completed in 83514ms
16538 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules@vue\cli\node_modules\chokidar\node_modules\fsevents):
16539 warn notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
16540 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid OS: darwin
16540 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Valid Arch: any
16540 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual OS: win32
16540 verbose notsup SKIPPING OPTIONAL DEPENDENCY: Actual Arch: x64
16541 warn @vue/compiler-sfc@3.0.5 requires a peer of vue@3.0.5 but none is installed. You must install peer dependencies yourself.
16542 verbose stack Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'
16543 verbose cwd C:\Users\User\Documents\Visual Studio Code\exp-vue
16544 verbose Windows_NT 10.0.19041
16545 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "@vue/cli"
16546 verbose node v15.6.0
16547 verbose npm v6.14.11
16548 error code EPERM
16549 error syscall mkdir
16550 error path C:\Program Files\nodejs\node_modules.staging
16551 error errno -4048
16552 error Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'
16552 error [OperationalError: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'] {
16552 error cause: [Error: EPERM: operation not permitted, mkdir 'C:\Program Files\nodejs\node_modules.staging'] {
16552 error errno: -4048,
16552 error code: 'EPERM',
16552 error syscall: 'mkdir',
16552 error path: 'C:\Program Files\nodejs\node_modules\.staging'
16552 error },
16552 error errno: -4048,
16552 error code: 'EPERM',
16552 error syscall: 'mkdir',
16552 error path: 'C:\Program Files\nodejs\node_modules\.staging',
16552 error parent: '@babel/core'
16552 error }
16553 error The operation was rejected by your operating system.
16553 error It's possible that the file was already in use (by a text editor or antivirus),
16553 error or that you lack permissions to access it.
16553 error
16553 error If you believe this might be a permissions issue, please double-check the
16553 error permissions of the file and its containing directories, or try running
16553 error the command again as root/Administrator.
16554 verbose exit [ -4048, true