Closed HariKiran9 closed 5 years ago
Couldn't reproduce locally just now on my MacBook. I suspect this is some sort of NPM permissions issue, see https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally and consider reinstalling npm with a node version manager such as nvm.
Getting below error message and unable to complete the install
/home/bc887d/dev/Shop/shop/node_modules/polymer-cli/node_modules/mkdirp/index.js:90 throw err0; ^
Error: EACCES: permission denied, mkdir '/home/bc887d/dev/Shop/shop/node_modules/polymer-cli/node_modules/wd/build' at Object.fs.mkdirSync (fs.js:885:18) at sync (/home/bc887d/dev/Shop/shop/node_modules/polymer-cli/node_modules/mkdirp/index.js:71:13) at Object. (/home/bc887d/dev/Shop/shop/node_modules/polymer-cli/node_modules/wd/scripts/build-browser-scripts.js:6:1)
at Module._compile (module.js:652:30)
at Object.Module._extensions..js (module.js:663:10)
at Module.load (module.js:565:32)
at tryModuleLoad (module.js:505:12)
at Function.Module._load (module.js:497:3)
at Function.Module.runMain (module.js:693:10)
at startup (bootstrap_node.js:188:16)
npm WARN @babel/plugin-transform-classes@7.0.0-beta.35 requires a peer of @babel/core@7.0.0-beta.35 but none is installed. You must install peer dependencies yourself.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/polymer-cli/node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! wd@1.11.0 install:
node scripts/build-browser-scripts
npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the wd@1.11.0 install script. npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in: npm ERR! /home/bc887d/.npm/_logs/2018-12-10T06_41_36_504Z-debug.log