Heroku npm bower issue mean stack app - node.js

I keep trying to push to heroku with no success. I have tried modifying the .gitignore file, sticking to node version 10, clearing npm cache, trying to stage instead of production, getting frustrated please help!
-----> Node.js app detected
-----> Resetting git environment
-----> Requested node range: 0.10.x
-----> Resolved node version: 0.10.35
-----> Downloading and installing node
-----> Found existing node_modules directory; skipping cache
-----> Rebuilding any native dependencies
npm ERR! Error: ENOENT, chmod '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/node-uuid/bin/uuid'
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Linux 3.8.11-ec2
npm ERR! command "/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/node" "/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/npm" "rebuild"
npm ERR! cwd /tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a
npm ERR! node -v v0.10.35
npm ERR! npm -v 1.4.28
npm ERR! path /tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/node-uuid/bin/uuid
npm ERR! code ENOENT
npm ERR! errno 34
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/npm-debug.log
npm ERR! not ok code 0
0 info it worked if it ends with ok
1 verbose cli [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/node',
1 verbose cli '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/npm',
1 verbose cli 'rebuild' ]
2 info using npm#1.4.28
3 info using node#v0.10.35
4 info readInstalled object
5 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a', 'cake#1.0.0' ]
6 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower',
6 verbose rebuild 'bower#1.3.12' ]
7 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/abbrev',
7 verbose rebuild 'abbrev#1.0.5' ]
8 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/archy',
8 verbose rebuild 'archy#0.0.2' ]
9 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-config',
9 verbose rebuild 'bower-config#0.5.2' ]
10 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-config/node_modules/graceful-fs',
10 verbose rebuild 'graceful-fs#2.0.3' ]
11 verbose rebuild path, id [ '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/mout',
11 verbose rebuild 'mout#0.9.1' ]
.......
667 verbose linkMans node-uuid#1.4.2
668 verbose rebuildBundles node-uuid#1.4.2
669 error Error: ENOENT, chmod '/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/node-uuid/bin/uuid'
670 error If you need help, you may report this *entire* log,
670 error including the npm and node versions, at:
670 error <http://github.com/npm/npm/issues>
671 error System Linux 3.8.11-ec2
672 error command "/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/node" "/tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/vendor/node/bin/npm" "rebuild"
673 error cwd /tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a
674 error node -v v0.10.35
675 error npm -v 1.4.28
676 error path /tmp/build_b8036af8fa11d1792ae4d166a4eaaf9a/node_modules/bower/node_modules/bower-registry-client/node_modules/request/node_modules/node-uuid/bin/uuid
677 error code ENOENT
678 error errno 34
679 verbose exit [ 34, true ]
! Push rejected, failed to compile Node.js app

Related

npm init doesn't work, ENOENT: no such file or directory

I install node 14(LTS) on my window10, and npm is auto install, but npm init isn't work.
I check version of them is work
C:\Users\RURU\Documents\practice\css> node -v
// 14.4
C:\Users\RURU\Documents\practice\css> npm -v
// 6
but, npm init does't work, when I want to init a package.json.
C:\Users\RURU\Documents\practice\css> npm init # neither npm init -y
Error :
npm ERR! code ENOENT
npm ERR! syscall open
npm ERR! path C:\Users\RURU\Documents\practice\css\package.json
npm ERR! errno -4058
npm ERR! enoent ENOENT: no such file or directory, open 'C:\Users\RURU\Documents\practice\css\package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\RURU\AppData\Local\npm-cache\_logs\2021-07-04T14_37_28_289Z-debug.log
Error log:
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'init'
1 verbose cli ]
2 info using npm#6.14.13
3 info using node#v14.17.2
4 silly package data {
4 silly package data name: 'c',
4 silly package data version: '1.0.0',
4 silly package data description: '',
4 silly package data main: 'index.js',
4 silly package data scripts: { test: 'echo "Error: no test specified" && exit 1' },
4 silly package data author: 'ru',
4 silly package data license: 'ISC'
4 silly package data }
5 info init written successfully
6 verbose stack Error: ENOENT: no such file or directory, open 'C:\Users\RURU\Documents\practice\css\package.json'
7 verbose cwd C:\Users\RURU\Documents\practice\css
8 verbose Windows_NT 10.0.19042
9 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "init"
10 verbose node v14.17.2
11 verbose npm v6.14.13
12 error code ENOENT
13 error syscall open
14 error path C:\Users\RURU\Documents\practice\css\package.json
15 error errno -4058
16 error enoent ENOENT: no such file or directory, open 'C:\Users\RURU\Documents\practice\css\package.json'
17 error enoent This is related to npm not being able to find a file.
18 verbose exit [ -4058, true ]
I dont't know how to fix it, can anyone help, please ...
my path
C:\Program Files\nodejs\;C:\Users\RURU\AppData\Roaming\npm
You can use 2 things to solve the problem :
Start the cmd in administrator mode and try again.
Run the command using --unsafe-perms i.e. npm init --unsafe-perms
I don't think 2 step will be required in most of the cases.

AzureDevOps pipeline - Nightwatch selenium standalone installation issue - Unable to run npm run 'e2e-setup' (contains 'selenium-standalone install')

I am trying to setup selenium standalone server with various browsers the script works fine on my local machine but same has issues working on Azure cloud using Azure DevOps tool.
From the logs (Detailed logs at the end) I see the below but not sure how to fix it:
2020-04-17T21:39:25.3581171Z Usage: selenium-standalone action [options]
2020-04-17T21:39:25.3581533Z
2020-04-17T21:39:25.3582171Z npm ERR! Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3582843Z npm ERR! argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3583217Z npm ERR! node v6.17.1
2020-04-17T21:39:25.3583400Z npm ERR! npm v3.10.10
2020-04-17T21:39:25.3583580Z npm ERR! code ELIFECYCLE
2020-04-17T21:39:25.3584038Z npm ERR! temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3584332Z npm ERR! Exit status 255
I have the below package.json:
{
"name": "temp",
"version": "1.0.0",
"description": "",
"main": "index.js",
"scripts": {
"test": "nightwatch",
"e2e-setup": "selenium-standalone install"
},
"keywords": [],
"author": "",
"license": "ISC",
"devDependencies": {
"#babel/core": "^7.9.0",
"#babel/preset-env": "^7.9.0",
"babel-core": "^6.26.3",
"babel-plugin-add-module-exports": "^1.0.2",
"babel-preset-env": "^1.7.0",
"babel-preset-es2015": "^6.24.1",
"gulp-babel": "^8.0.0-beta.2",
"selenium-standalone": "^6.17.0"
},
"dependencies": {
"easy-soap-request": "^3.2.2",
"nightwatch": "^1.3.4",
"xmldom": "^0.3.0"
}
}
on VScode when I run
npm install nightwatch
npm install selenium-standalone
and
npm run e2e-setup
I do not have any issues when I try the above on my machine - Selenium server jar and all the browser (chrome, firefox, ie, edge) binaries are getting downloaded)
The above setup is as mentioned in the official seleinum-standalone npm website (https://www.npmjs.com/package/selenium-standalone#install--run)
My Azure CI setup:
But when I try the same on Azure DevOps tool (Running the same on Azure cloud) I am having issues like below:
2020-04-17T21:39:22.1913471Z ##[section]Starting: npm run e2e-setup
2020-04-17T21:39:22.1923363Z ==============================================================================
2020-04-17T21:39:22.1923659Z Task : npm
2020-04-17T21:39:22.1924046Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Azure Artifacts.
2020-04-17T21:39:22.1924428Z Version : 1.166.1
2020-04-17T21:39:22.1924652Z Author : Microsoft Corporation
2020-04-17T21:39:22.1924983Z Help : https://learn.microsoft.com/azure/devops/pipelines/tasks/package/npm
2020-04-17T21:39:22.1925348Z ==============================================================================
2020-04-17T21:39:22.5235427Z SYSTEMVSSCONNECTION exists true
2020-04-17T21:39:22.7105531Z SYSTEMVSSCONNECTION exists true
2020-04-17T21:39:22.7890296Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm --version
2020-04-17T21:39:23.0268360Z 3.10.10
2020-04-17T21:39:23.9587311Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm config list
2020-04-17T21:39:24.4295571Z ; cli configs
2020-04-17T21:39:24.4297644Z user-agent = "npm/3.10.10 node/v6.17.1 linux x64"
2020-04-17T21:39:24.4298039Z
2020-04-17T21:39:24.4298357Z ; environment configs
2020-04-17T21:39:24.4298785Z userconfig = "/vsts/agent/_work/_temp/npm/830.npmrc"
2020-04-17T21:39:24.4299106Z
2020-04-17T21:39:24.4299481Z ; node bin location = /vsts/agent/_work/_tool/node/6.17.1/x64/bin/node
2020-04-17T21:39:24.4300000Z ; cwd = /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:24.4300385Z ; HOME = /root
2020-04-17T21:39:24.4301230Z ; "npm config ls -l" to show all defaults.
2020-04-17T21:39:24.4301526Z
2020-04-17T21:39:24.4304850Z [command]/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm run e2e-setup
2020-04-17T21:39:25.3579514Z not found: java
2020-04-17T21:39:25.3579860Z
2020-04-17T21:39:25.3581171Z Usage: selenium-standalone action [options]
2020-04-17T21:39:25.3581533Z
2020-04-17T21:39:25.3582171Z npm ERR! Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3582843Z npm ERR! argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3583217Z npm ERR! node v6.17.1
2020-04-17T21:39:25.3583400Z npm ERR! npm v3.10.10
2020-04-17T21:39:25.3583580Z npm ERR! code ELIFECYCLE
2020-04-17T21:39:25.3584038Z npm ERR! temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3584332Z npm ERR! Exit status 255
2020-04-17T21:39:25.3584511Z npm ERR!
2020-04-17T21:39:25.3584965Z npm ERR! Failed at the temp#1.0.0 e2e-setup script 'selenium-standalone install'.
2020-04-17T21:39:25.3585333Z npm ERR! Make sure you have the latest version of node.js and npm installed.
2020-04-17T21:39:25.3585684Z npm ERR! If you do, this is most likely a problem with the temp package,
2020-04-17T21:39:25.3585947Z npm ERR! not with npm itself.
2020-04-17T21:39:25.3586231Z npm ERR! Tell the author that this fails on your system:
2020-04-17T21:39:25.3586678Z npm ERR! selenium-standalone install
2020-04-17T21:39:25.3587020Z npm ERR! You can get information on how to open an issue for this project with:
2020-04-17T21:39:25.3587342Z npm ERR! npm bugs temp
2020-04-17T21:39:25.3587803Z npm ERR! Or if that isn't available, you can get their info via:
2020-04-17T21:39:25.3588109Z npm ERR! npm owner ls temp
2020-04-17T21:39:25.3588351Z npm ERR! There is likely additional logging output above.
2020-04-17T21:39:25.3588530Z
2020-04-17T21:39:25.3588791Z npm ERR! Please include the following file with any support request:
2020-04-17T21:39:25.3589311Z npm ERR! /vsts/agent/_work/r2/a/_QA_IDLookUp/npm-debug.log
2020-04-17T21:39:25.3590596Z > temp#1.0.0 e2e-setup /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3591763Z > selenium-standalone install
2020-04-17T21:39:25.3592087Z
2020-04-17T21:39:25.3734932Z Found npm debug log, make sure the path matches with the one in npm's output: /vsts/agent/_work/r2/a/_QA_IDLookUp/npm-debug.log
2020-04-17T21:39:25.3735698Z 0 info it worked if it ends with ok
2020-04-17T21:39:25.3737184Z 1 verbose cli [ '/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node',
2020-04-17T21:39:25.3738213Z 1 verbose cli '/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm',
2020-04-17T21:39:25.3739010Z 1 verbose cli 'run',
2020-04-17T21:39:25.3739677Z 1 verbose cli 'e2e-setup' ]
2020-04-17T21:39:25.3740072Z 2 info using npm#3.10.10
2020-04-17T21:39:25.3740401Z 3 info using node#v6.17.1
2020-04-17T21:39:25.3741309Z 4 verbose run-script [ 'pree2e-setup', 'e2e-setup', 'poste2e-setup' ]
2020-04-17T21:39:25.3742292Z 5 info lifecycle temp#1.0.0~pree2e-setup: temp#1.0.0
2020-04-17T21:39:25.3743416Z 6 silly lifecycle temp#1.0.0~pree2e-setup: no script for pree2e-setup, continuing
2020-04-17T21:39:25.3744395Z 7 info lifecycle temp#1.0.0~e2e-setup: temp#1.0.0
2020-04-17T21:39:25.3745399Z 8 verbose lifecycle temp#1.0.0~e2e-setup: unsafe-perm in lifecycle true
2020-04-17T21:39:25.3747409Z 9 verbose lifecycle temp#1.0.0~e2e-setup: PATH: /vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/bin/node-gyp-bin:/vsts/agent/_work/r2/a/_QA_IDLookUp/node_modules/.bin:/vsts/agent/_work/_tool/node/6.17.1/x64/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
2020-04-17T21:39:25.3749200Z 10 verbose lifecycle temp#1.0.0~e2e-setup: CWD: /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3750457Z 11 silly lifecycle temp#1.0.0~e2e-setup: Args: [ '-c', 'selenium-standalone install' ]
2020-04-17T21:39:25.3751608Z 12 silly lifecycle temp#1.0.0~e2e-setup: Returned: code: 255 signal: null
2020-04-17T21:39:25.3752743Z 13 info lifecycle temp#1.0.0~e2e-setup: Failed to exec e2e-setup script
2020-04-17T21:39:25.3753814Z 14 verbose stack Error: temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3754348Z 14 verbose stack Exit status 255
2020-04-17T21:39:25.3755003Z 14 verbose stack at EventEmitter.<anonymous> (/vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
2020-04-17T21:39:25.3755744Z 14 verbose stack at emitTwo (events.js:106:13)
2020-04-17T21:39:25.3756353Z 14 verbose stack at EventEmitter.emit (events.js:191:7)
2020-04-17T21:39:25.3757140Z 14 verbose stack at ChildProcess.<anonymous> (/vsts/agent/_work/_tool/node/6.17.1/x64/lib/node_modules/npm/lib/utils/spawn.js:40:14)
2020-04-17T21:39:25.3757834Z 14 verbose stack at emitTwo (events.js:106:13)
2020-04-17T21:39:25.3758420Z 14 verbose stack at ChildProcess.emit (events.js:191:7)
2020-04-17T21:39:25.3759038Z 14 verbose stack at maybeClose (internal/child_process.js:920:16)
2020-04-17T21:39:25.3759714Z 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
2020-04-17T21:39:25.3760203Z 15 verbose pkgid temp#1.0.0
2020-04-17T21:39:25.3760616Z 16 verbose cwd /vsts/agent/_work/r2/a/_QA_IDLookUp
2020-04-17T21:39:25.3761457Z 17 error Linux 5.0.0-1031-azure
2020-04-17T21:39:25.3762546Z 18 error argv "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/node" "/vsts/agent/_work/_tool/node/6.17.1/x64/bin/npm" "run" "e2e-setup"
2020-04-17T21:39:25.3763170Z 19 error node v6.17.1
2020-04-17T21:39:25.3763496Z 20 error npm v3.10.10
2020-04-17T21:39:25.3763826Z 21 error code ELIFECYCLE
2020-04-17T21:39:25.3764642Z 22 error temp#1.0.0 e2e-setup: `selenium-standalone install`
2020-04-17T21:39:25.3765087Z 22 error Exit status 255
2020-04-17T21:39:25.3765921Z 23 error Failed at the temp#1.0.0 e2e-setup script 'selenium-standalone install'.
2020-04-17T21:39:25.3766518Z 23 error Make sure you have the latest version of node.js and npm installed.
2020-04-17T21:39:25.3767106Z 23 error If you do, this is most likely a problem with the temp package,
2020-04-17T21:39:25.3767909Z 23 error not with npm itself.
2020-04-17T21:39:25.3768396Z 23 error Tell the author that this fails on your system:
2020-04-17T21:39:25.3769248Z 23 error selenium-standalone install
2020-04-17T21:39:25.3769864Z 23 error You can get information on how to open an issue for this project with:
2020-04-17T21:39:25.3770358Z 23 error npm bugs temp
2020-04-17T21:39:25.3771224Z 23 error Or if that isn't available, you can get their info via:
2020-04-17T21:39:25.3771966Z 23 error npm owner ls temp
2020-04-17T21:39:25.3772352Z 23 error There is likely additional logging output above.
2020-04-17T21:39:25.3772813Z 24 verbose exit [ 1, true ]
2020-04-17T21:39:25.3773034Z
2020-04-17T21:39:25.3775507Z ##[error]Error: Npm failed with return code: 1
2020-04-17T21:39:25.3816759Z ##[section]Finishing: npm run e2e-setup
The version of node and npm seem to be very old. I have been running nightwatch tests using selenium on travis, azure devops and github actions. My advice is to have the configuration through a yml file which is very simple. You can see mine in the below link and try it.
Reference: https://github.com/spnraju/nightwatchjs-selenium-example/blob/master/azure-pipelines.yml

Can't install any packages with Node.js [duplicate]

This question already has answers here:
Error: Cannot find module '#ionic/app-scripts'
(18 answers)
Closed 3 years ago.
I'm an absolute novice in Ionic, Cordova and Node.js.
I have the following problem with Node.js:
I got a project from a colleague created with ionic and cordova. The app itself is also running, for a special customer, we have adapted the design. My thought was that it was done quickly. I changed my branch in GIT to the corresponding project and wanted to do it. Unfortunately, I get countless error messages and warnings that I did not have in the previous project.
I uninstalled Node.js and reinstalled it completely, unfortunately nothing has changed. I can not uninstall or install any of the packages. I always get this eternally long error message and I do not know exactly what the problem is. Uninstalling Ionic and cordova does not work either, same error message. Below is a listing of my version of Node.js, Ionic and cordova and the beginning and end of the error message.
Console:gitproject user$ git branch
* development
master
Console:gitproject user$ ionic cordova build
? What platform would you like to build (android, ios): ios
> ionic-app-scripts build --target cordova --platform ios
[08:44:43] ionic-app-scripts 3.2.3
[08:44:43] build dev started ...
[08:44:43] clean started ...
[08:44:43] clean finished in 24 ms
[08:44:43] copy started ...
[08:44:43] deeplinks started ...
[08:44:44] deeplinks finished in 593 ms
[08:44:44] transpile started ...
[08:44:56] typescript: src/app/app.component.ts, line: 34
Cannot find name 'Globalization'.
L33: private translate: TranslateService,
L34: private globalization: Globalization) {
L35: platform.ready().then(() => {
[08:44:56] ionic-app-script task: "build"
[08:44:56] Error: Failed to transpile program
Error: Failed to transpile program
at new BuildError (/path/to/project/gitproject/node_modules/#ionic/app-scripts/dist/util/errors.js:16:28)
at /path/to/project/gitproject/node_modules/#ionic/app-scripts/dist/transpile.js:159:20
at new Promise (<anonymous>)
at transpileWorker (/path/to/project/gitproject/node_modules/#ionic/app-scripts/dist/transpile.js:107:12)
at Object.transpile (/path/to/project/gitproject/node_modules/#ionic/app-scripts/dist/transpile.js:64:12)
at /path/to/project/gitproject/node_modules/#ionic/app-scripts/dist/build.js:109:82
[ERROR] An error occurred while running subprocess ionic-app-scripts.
ionic-app-scripts build --target cordova --platform ios exited with exit code 1.
Re-running this command with the --verbose flag may provide more information.
Console:gitproject user$ ionic cordova plugin add cordova-plugin-globalization
> cordova plugin add cordova-plugin-globalization --save
Installing "cordova-plugin-globalization" for ios
Unable to load PlatformApi from platform. Error: Cannot find module 'unorm'
Require stack:
- /path/to/project/gitproject/platforms/ios/cordova/Api.js
- /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/util.js
- /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/platforms/platforms.js
- /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/install.js
- /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/plugman.js
- /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/cordova-lib.js
- /usr/local/lib/node_modules/cordova/src/help.js
- /usr/local/lib/node_modules/cordova/src/cli.js
- /usr/local/lib/node_modules/cordova/bin/cordova
Failed to install 'cordova-plugin-globalization': Error [ERR_UNHANDLED_ERROR]: Unhandled error. ('The platform "ios" does not appear to be a valid ' +
'cordova platform. It is missing API.js. ios not ' +
'supported.')
at CordovaEventEmitter.emit (events.js:185:17)
at CordovaEventEmitter.emit (/usr/local/lib/node_modules/cordova/node_modules/cordova-common/src/events.js:69:22)
at Object.getPlatformApiFunction (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/cordova/util.js:384:20)
at Object.getPlatformApi (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/platforms/platforms.js:55:32)
at handleInstall (/usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/install.js:580:29)
at /usr/local/lib/node_modules/cordova/node_modules/cordova-lib/src/plugman/install.js:349:28
at processTicksAndRejections (internal/process/task_queues.js:89:5)
Unhandled error. ('The platform "ios" does not appear to be a valid ' +
'cordova platform. It is missing API.js. ios not ' +
'supported.')
Console:gitproject user$ npm install #ionic-native/globalization
> fsevents#1.2.4 install /path/to/project/gitproject/node_modules/fsevents
> node install
node-pre-gyp WARN Tried to download(404): https://fsevents-binaries.s3-us-west-2.amazonaws.com/v1.2.4/fse-v1.2.4-node-v72-darwin-x64.tar.gz
node-pre-gyp WARN Pre-built binaries not found for fsevents#1.2.4 and node#12.2.0 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
...
...
...
...
10 warnings and 8 errors generated.
make: *** [Release/obj.target/binding/src/binding.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack at ChildProcess.onExit (/path/to/project/gitproject/node_modules/node-gyp/lib/build.js:262:23)
gyp ERR! stack at ChildProcess.emit (events.js:200:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:272:12)
gyp ERR! System Darwin 18.6.0
gyp ERR! command "/usr/local/bin/node" "/path/to/project/gitproject/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library="
gyp ERR! cwd /path/to/project/gitproject/node_modules/node-sass
gyp ERR! node -v v12.3.1
gyp ERR! node-gyp -v v3.7.0
gyp ERR! not ok
Build failed with error code: 1
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules/fsevents):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 install: `node install`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! node-sass#4.9.0 postinstall: `node scripts/build.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the node-sass#4.9.0 postinstall 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! /path/to/user/folder/.npm/_logs/2019-05-27T08_04_02_672Z-debug.log
Here is the edition from the above mentioned error log
2653 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 (node_modules/fsevents):
2654 warn optional SKIPPING OPTIONAL DEPENDENCY: fsevents#1.2.4 install: `node install`
2654 warn optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
2655 verbose optional SKIPPING OPTIONAL DEPENDENCY:
2655 verbose optional Failed at the fsevents#1.2.4 install script.
2655 verbose optional SKIPPING OPTIONAL DEPENDENCY: This is probably not a problem with npm. There is likely additional logging output above.
2656 verbose stack Error: node-sass#4.9.0 postinstall: `node scripts/build.js`
2656 verbose stack Exit status 1
2656 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:301:16)
2656 verbose stack at EventEmitter.emit (events.js:200:13)
2656 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
2656 verbose stack at ChildProcess.emit (events.js:200:13)
2656 verbose stack at maybeClose (internal/child_process.js:1021:16)
2656 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:283:5)
2657 verbose pkgid node-sass#4.9.0
2658 verbose cwd /Users/premox/Documents/projects/gitproject
2659 verbose Darwin 18.6.0
2660 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "uninstall" "sass"
2661 verbose node v12.3.1
2662 verbose npm v6.9.0
2663 error code ELIFECYCLE
2664 error errno 1
2665 error node-sass#4.9.0 postinstall: `node scripts/build.js`
2665 error Exit status 1
2666 error Failed at the node-sass#4.9.0 postinstall script.
2666 error This is probably not a problem with npm. There is likely additional logging output above.
2667 verbose exit [ 1, true ]
Console:gitproject user$ node -v
v12.3.1
Console:gitproject user$ npm -v
6.9.0
Can someone explain this error message to me?
There are a couple of things you can do in order to setup the project correctly.
Check if node, ionic and cordova are properly installed.
Completely delete the node modules folder and then run the following command:-
npm install
This would install all the dependencies in the project.
If above doesnot work then you can try, same step mentioned by Ashok to resolve:-
npm install #ionic/app-scripts#latest --save-dev
Please let me know if you have any questions.

not able to install npm without sudo

I've installed node into a custom directory in my home folder called local per these instructions : https://gist.github.com/isaacs/579814
I've added the location to my PATH and it seems to work fine. I cannot however seem to get npm to install without sudo. From what I can tell it is trying to execute a command in /bin folder.
The command I am running from ~/local/npm is make install and I got the latest versions of both node and npm from github.
Can anyone assist here?
user#localhost [~/local/npm]# make install
rm -rf \
.building_ronn \
html/doc \
html/api \
man
scripts/doc-build.sh doc/api/npm-view.md man/man3/npm-view.3
make[1]: Entering directory `/home1/extrabol/local/npm'
node cli.js install ronn --no-global
npm ERR! Error: EROFS, mkdir '/bin/node'
npm ERR! at Error (native)
npm ERR! If you need help, you may report this *entire* log,
npm ERR! including the npm and node versions, at:
npm ERR! <http://github.com/npm/npm/issues>
npm ERR! System Linux 3.4.87-20140414.1.bh6.x86_64
npm ERR! command "node" "/home1/extrabol/local/npm/cli.js" "install" "ronn" "--no-global"
npm ERR! cwd /home1/extrabol/local/npm
npm ERR! node -v v0.11.14-pre
npm ERR! npm -v 1.4.10
npm ERR! path /bin/node
npm ERR! code EROFS
npm ERR! errno -30
npm ERR!
npm ERR! Additional logging details can be found in:
npm ERR! /home1/extrabol/local/npm/npm-debug.log
npm ERR! not ok code 0
The Debug Log reports this
0 info it worked if it ends with ok
1 verbose cli [ 'node',
1 verbose cli '/home1/extrabol/local/npm/cli.js',
1 verbose cli 'install',
1 verbose cli 'ronn',
1 verbose cli '--no-global' ]
2 info using npm#1.4.10
3 info using node#v0.11.14-pre
4 verbose node symlink /home1/extrabol/local/node/node
5 error Error: EROFS, mkdir '/bin/node'
5 error at Error (native)
6 error If you need help, you may report this *entire* log,
6 error including the npm and node versions, at:
6 error <http://github.com/npm/npm/issues>
7 error System Linux 3.4.87-20140414.1.bh6.x86_64
8 error command "node" "/home1/extrabol/local/npm/cli.js" "install" "ronn" "--no-global"
9 error cwd /home1/extrabol/local/npm
10 error node -v v0.11.14-pre
11 error npm -v 1.4.10
12 error path /bin/node
13 error code EROFS
14 error errno -30
Figured it out. Looks like when I git cloned the npm files somehow I didn't have ownership over all of the files. a quick chown -R on the npm folder fixed the issue.

npm start gives the error that server.js is not a valid win32 application

I'm trying to start the application server for a group project I'm doing. I posted my error below and I'll copy the npm-debug.log contents below.
This works perfectly fine my teammates mac laptop. I'm trying to run this on a Windows 8 64 bit machine. I tried with both the 32 bit and 64 bit binaries of node and it gives the same output.
output from npm start
Windows PowerShell Copyright (C) 2013 Microsoft Corporation. All
rights reserved.
C:\Users\damien\Documents\GitHub\lend [development]> npm start
lending-app#0.0.1 start C:\Users\damien\Documents\GitHub\lend
brunch watch --server
05 Apr 22:01:49 - error: couldn't load server lend.js: Error: %1 is
not a valid Win32 application.
C:\Users\damien\Documents\GitHub\lend\node_modules\client-sessions\node_modules\node-proxy\build\Release\nodeproxy.node
C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\lib\watch.js:105
if (server.startServer == null) {
^ TypeError: Cannot read property 'startServer' of undefined
at startServer (C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\lib\watch.js:105:17)
at C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\lib\watch.js:418:18
at C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\lib\helpers.js:475:14
at C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\node_modules\read-components\index.js:207:16
at C:\Users\damien\AppData\Roaming\npm\node_modules\brunch\node_modules\read-components\index.js:34:14
at Object.cb [as oncomplete] (fs.js:168:19)
npm ERR! lending-app#0.0.1 start: brunch watch --server npm ERR!
Exit status 8 npm ERR! npm ERR! Failed at the lending-app#0.0.1 start
script. npm ERR! This is most likely a problem with the lending-app
package, npm ERR! not with npm itself. npm ERR! Tell the author that
this fails on your system: npm ERR! brunch watch --server npm ERR!
You can get their info via: npm ERR! npm owner ls lending-app npm
ERR! There is likely additional logging output above. npm ERR! System
Windows_NT 6.2.9200 npm ERR! command "C:\Program
Files\nodejs\\node.exe" "C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js" "start" npm ERR!
cwd C:\Users\damien\Documents\GitHub\lend npm ERR! node -v v0.10.26
npm ERR! npm -v 1.4.3 npm ERR! code ELIFECYCLE npm ERR! npm ERR!
Additional logging details can be found in: npm ERR!
C:\Users\damien\Documents\GitHub\lend\npm-debug.log npm ERR! not ok
code 0 C:\Users\damien\Documents\GitHub\lend [development]>
npm-debug.log
0 info it worked if it ends with ok
1 verbose cli [ 'C:\Program Files\nodejs\\node.exe',
1 verbose cli 'C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'start' ]
2 info using npm#1.4.3
3 info using node#v0.10.26
4 verbose node symlink C:\Program Files\nodejs\node.exe
5 verbose run-script [ 'prestart', 'start', 'poststart' ]
6 info prestart lending-app#0.0.1
7 info start lending-app#0.0.1
8 verbose unsafe-perm in lifecycle true
9 info lending-app#0.0.1 Failed to exec start script
10 error lending-app#0.0.1 start: brunch watch --server
10 error Exit status 8
11 error Failed at the lending-app#0.0.1 start script.
11 error This is most likely a problem with the lending-app package,
11 error not with npm itself.
11 error Tell the author that this fails on your system:
11 error brunch watch --server
11 error You can get their info via:
11 error npm owner ls lending-app
11 error There is likely additional logging output above.
12 error System Windows_NT 6.2.9200
13 error command "C:\Program Files\nodejs\\node.exe" "C:\Program
Files\nodejs\node_modules\npm\bin\npm-cli.js" "start"
14 error cwd C:\Users\damien\Documents\GitHub\lend
15 error node -v v0.10.26
16 error npm -v 1.4.3
17 error code ELIFECYCLE
18 verbose exit [ 1, true ]
npm start calls the scripts.start entry in your package.json file. In this case it looks like the command is brunch watch --server. Chances are you are missing the brunch binary which is causing npm to spit out the error.

Resources