I would like to try and setup Reaction Commerce this reaction-doc. When I run reaction init, NPM error occurs in installing NPM packages.
5868 verbose stack Error: Command failed: git -c core.longpaths=true clone --template=C:\Users\..\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git#github.com:ongoworks/node-authorize-net.git C:\Users\..\AppData\Roaming\npm-cache\_git-remotes\git-github-com-ongoworks-node-authorize-net-git-e88b3c4b
5868 verbose stack Cloning into bare repository 'C:\Users\...\AppData\Roaming\npm-cache\_git-remotes\git-github-com-ongoworks-node-authorize-net-git-e88b3c4b'...
5868 verbose stack Host key verification failed.
5868 verbose stack fatal: Could not read from remote repository.
5868 verbose stack
5868 verbose stack Please make sure you have the correct access rights
5868 verbose stack and the repository exists.
5868 verbose stack
5868 verbose stack at ChildProcess.exithandler (child_process.js:213:12)
5868 verbose stack at emitTwo (events.js:87:13)
5868 verbose stack at ChildProcess.emit (events.js:172:7)
5868 verbose stack at maybeClose (internal/child_process.js:829:16)
5868 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:211:5)
5869 verbose cwd C:\Users\...\reaction
5870 error Windows_NT 6.1.7600
5871 error argv "C:\\Users\\...\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.1_1\\mt-os.windows.x86_32\\dev_bundle\\bin\\node.exe" "C:\\Users\\...\\AppData\\Local\\.meteor\\packages\\meteor-tool\\1.4.1_1\\mt-os.windows.x86_32\\dev_bundle\\lib\\node_modules\\npm\\bin\\npm-cli.js" "install"
5872 error node v4.5.0
5873 error npm v3.10.6
5874 error code 128
5875 error Command failed: git -c core.longpaths=true clone --template=C:\Users\...\AppData\Roaming\npm-cache\_git-remotes\_templates --mirror git#github.com:ongoworks/node-authorize-net.git C:\Users\...\AppData\Roaming\npm-cache\_git-remotes\git-github-com-ongoworks-node-authorize-net-git-e88b3c4b
5875 error Cloning into bare repository 'C:\Users\...\AppData\Roaming\npm-cache\_git-remotes\git-github-com-ongoworks-node-authorize-net-git-e88b3c4b'...
5875 error Host key verification failed.
5875 error fatal: Could not read from remote repository.
5875 error
5875 error Please make sure you have the correct access rights
5875 error and the repository exists.
5876 error If you need help, you may report this error at:
5876 error <https://github.com/npm/npm/issues>
5877 verbose exit [ 1, true ]
I found Host key verification failed and Please make sure you have the correct access rights. I already created ssh key in my github account. I can login successfully from Git Bash command(ssh -T git#github.com).
Do I need special access key for reaction commerce? I am confused this problem is git bash configuration problem or key verification problem in Reaction. Cos I have no experience in bit bash command.
Related
I have provider/gcp directroy containing its own package.json in my nodejs application.
In my root package.json, I have a script like this:
"installGCP": "npm i provier/gcp".
I want to install provider/gcp dependencies into root node_modules folder only.
On my local, its working fine. But through build pipeline, its failing with error code 128.
verbose stack Error: An unknown git error occurred
1173 verbose stack at makeError (/usr/lib/node_modules/npm/node_modules/#npmcli/git/lib/make-error.js:28:13)
1173 verbose stack at /usr/lib/node_modules/npm/node_modules/#npmcli/git/lib/spawn.js:36:26
1173 verbose stack at runMicrotasks (<anonymous>)
1173 verbose stack at processTicksAndRejections (node:internal/process/task_queues:96:5)
1174 verbose cwd /var/vsts/2/s
1175 verbose Linux 4.19.167+
1176 verbose argv "/usr/bin/node" "/usr/bin/npm" "i" "provider/gcp"
1177 verbose node v16.13.0
1178 verbose npm v8.1.0
1179 error code 128
1180 error An unknown git error occurred
1181 error command git --no-replace-objects ls-remote ssh://git#github.com/provider/gcp.git
1182 error Warning: Permanently added the ECDSA host key for IP address '140.82.112.3' to the list of known hosts.
1182 error git#github.com: Permission denied (publickey).
1182 error fatal: Could not read from remote repository.
1182 error
1182 error Please make sure you have the correct access rights
1182 error and the repository exists.
1183 verbose exit 128
I have already tried this option based on recommendation on some other forums, but it did not work either.
"installGCP": "git config --global url.'https://'.insteadOf git:// && npm i provider/gcp"
I see this issue when I run npm script through tfs build but when I run the above directly tfs build machine I don't see any error.
Note: I use node -v 8.12.0 and npm -v 6.4.1
I tried to find the reason for this error I didn't find resource explaining me the reason for this error
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\cygwin64\home\licbuild\ANSYSDev\LicensingPortal\node\node-v8.12.0-win-x64\node_modules\npm\node_modules\npm-lifecycle\index.js:301:16)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at EventEmitter.emit (events.js:214:7)
13 verbose stack at ChildProcess.<anonymous> (C:\cygwin64\home\licbuild\ANSYSDev\LicensingPortal\node\node-v8.12.0-win-x64\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at emitTwo (events.js:126:13)
13 verbose stack at ChildProcess.emit (events.js:214:7)
13 verbose stack at maybeClose (internal/child_process.js:915:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
If you are able to run the script through TFS build machine directly but failed through TFS build.
This may caused by permission of your build service account such as local Admin. You may use a different account to remote build machine and run the script other than your build service account.
To narrow down the issue, you could also use build service account directly login your build machine and try to run the script again if still get same result.
Besides, you could also set system.debug=true to get a more detail build log for troubleshooting.
Problem
Failed at the ffmpeg-binaries#4.0.0 install script 'node install'
How I do it
npm i ffmpeg-binaries
Environment
Ubuntu 14 on VDS
Node v6.0.0
NVM v3.8.6
Last string of npm-debug
9491 silly rollbackFailedOptional Starting
9492 silly rollbackFailedOptional Finishing
9493 silly runTopLevelLifecycles Starting
9494 silly runTopLevelLifecycles Finishing
9495 silly install printInstalled
9496 warn root#1.0.0 No description
9497 warn root#1.0.0 No repository field.
9498 verbose stack Error: ffmpeg-binaries#4.0.0 install: `node install`
9498 verbose stack Exit status 137
9498 verbose stack at EventEmitter.<anonymous> (/root/.nvm/versions/node/v6.0.0/lib/node_modules/npm/lib/utils/lifecycle.js:239:16)
9498 verbose stack at emitTwo (events.js:106:13)
9498 verbose stack at EventEmitter.emit (events.js:191:7)
9498 verbose stack at ChildProcess.<anonymous> (/root/.nvm/versions/node/v6.0.0/lib/node_modules/npm/lib/utils/spawn.js:24:14)
9498 verbose stack at emitTwo (events.js:106:13)
9498 verbose stack at ChildProcess.emit (events.js:191:7)
9498 verbose stack at maybeClose (internal/child_process.js:850:16)
9498 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
9499 verbose pkgid ffmpeg-binaries#4.0.0
9500 verbose cwd /root
9501 error Linux 2.6.32-042stab127.2
9502 error argv "/root/.nvm/versions/node/v6.0.0/bin/node" "/root/.nvm/versions/node/v6.0.0/bin/npm" "i" "ffmpeg-binaries"
9503 error node v6.0.0
9504 error npm v3.8.6
9505 error code ELIFECYCLE
9506 error ffmpeg-binaries#4.0.0 install: `node install`
9506 error Exit status 137
9507 error Failed at the ffmpeg-binaries#4.0.0 install script 'node install'.
9507 error Make sure you have the latest version of node.js and npm installed.
9507 error If you do, this is most likely a problem with the ffmpeg-binaries package,
9507 error not with npm itself.
9507 error Tell the author that this fails on your system:
9507 error node install
9507 error You can get information on how to open an issue for this project with:
9507 error npm bugs ffmpeg-binaries
9507 error Or if that isn't available, you can get their info via:
9507 error npm owner ls ffmpeg-binaries
9507 error There is likely additional logging output above.
9508 verbose exit [ 1, true ]
I have also recently been having this error, but I have since solved it. The thing you need to do is use the command:
npm install ffbinaries
instead of using ffmpeg-binaries.
The reason for this is because the binaries were originally created for ubuntu linux. Hope this helps! :)
npm ERR! code E400
npm ERR! 400 Bad Request: typescript#https://registry.npmjs.org/typescript/-/typescript-2.6.2.tgz
npm ERR! A complete log of this run can be found in:
npm ERR! /home/david/.npm/_logs/2018-06-01T08_01_21_010Z-debug.log
I get this Error when I start npm i without sudo. With sudo it works fine. I fixed all the permissions, installed node without sudo, but the error still occurs.
node -v
v8.11.2
npm -v
5.6.0
Edit1:
Here are the last lines of the logfile:
9991 verbose stack Error: 400 Bad Request: typescript#https://registry.npmjs.org/typescript/-/typescript-2.6.2.tgz
9991 verbose stack at fetch.then.res (/usr/lib64/node_modules/npm8/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
9991 verbose stack at tryCatcher (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/util.js:16:23)
9991 verbose stack at Promise._settlePromiseFromHandler (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/promise.js:512:31)
9991 verbose stack at Promise._settlePromise (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/promise.js:569:18)
9991 verbose stack at Promise._settlePromise0 (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/promise.js:614:10)
9991 verbose stack at Promise._settlePromises (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/promise.js:693:18)
9991 verbose stack at Async._drainQueue (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/async.js:133:16)
9991 verbose stack at Async._drainQueues (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/async.js:143:10)
9991 verbose stack at Immediate.Async.drainQueues (/usr/lib64/node_modules/npm8/node_modules/bluebird/js/release/async.js:17:14)
9991 verbose stack at runCallback (timers.js:810:20)
9991 verbose stack at tryOnImmediate (timers.js:768:5)
9991 verbose stack at processImmediate [as _immediateCallback] (timers.js:745:5)
9992 verbose cwd /home/david/Dev/Projects/MobileInfoApp/LHMobileApp
9993 verbose Linux 4.16.12-1-default
9994 verbose argv "/usr/bin/node8" "/usr/bin/npm-default" "i"
9995 verbose node v8.11.2
9996 verbose npm v5.6.0
9997 error code E400
9998 error 400 Bad Request: typescript#https://registry.npmjs.org/typescript/-/typescript-2.6.2.tgz
9999 verbose exit [ 1, true ]
Edit2: I reinstalled node again and followed a guide, I get a diffrent error now:
Unhandled rejection Error: invalid config key requested: singleuffer#5.1.2 extracted to /home/david/Dev/Projects/MobileInfoApp/LHMobileApp/n
at pudGet (/usr/local/lib/node_modules/npm/node_modules/figgy-pudding/index.js:31:11)
at FiggyPudding.get (/usr/local/lib/node_modules/npm/node_modules/figgy-pudding/index.js:13:12)
at Object.get (/usr/local/lib/node_modules/npm/node_modules/figgy-pudding/index.js:71:16)
at _parse (/usr/local/lib/node_modules/npm/node_modules/ssri/index.js:138:12)
at parse (/usr/local/lib/node_modules/npm/node_modules/ssri/index.js:125:12)
at Object.checkData (/usr/local/lib/node_modules/npm/node_modules/ssri/index.js:216:9)
at write (/usr/local/lib/node_modules/npm/node_modules/cacache/lib/content/write.js:34:31)
at putData (/usr/local/lib/node_modules/npm/node_modules/cacache/put.js:25:10)
at Object.x.put (/usr/local/lib/node_modules/npm/node_modules/cacache/locales/en.js:28:37)
at readFileAsync.then.data (/usr/local/lib/node_modules/npm/node_modules/pacote/lib/fetchers/file.js:38:28)
at tryCatcher (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
at Promise._settlePromiseFromHandler (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
at Promise._settlePromise (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
at Promise._settlePromise0 (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
at Promise._settlePromises (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
at Promise._fulfill (/usr/local/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:638:18)
npm ERR! cb() never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/npm/issues>
npm ERR! A complete log of this run can be found in:
npm ERR! /home/david/.npm/_logs/2018-06-04T07_53_53_015Z-debug.log
This is definitely folder permission issue. There are multiple ways for solving this, which is explained in detail in this article.
Installing global node modules (Linux and Mac)
For Debian Distros, following should let you run npm install without sudo.
Change your npm prefix to somewhere that your user has permission to write to
npm config set prefix=$HOME/david/
Then run the following and add it to .bashrc
export PATH=$HOME/david/bin:$PATH
Take ownership of /usr/local
sudo chown -R $USER /usr/local
Credit goes here
I'm using jade-cli to compile my project from .jade files into .html.
Jade files have following hierarchy:
components
views
templates
...
I want rendered result to have same folder structure and trying to use -H attribute as it is said in documentation here: https://www.npmjs.com/package/jade-cli
However when I'm using command jade -P -H src -o dst npm returns following error:
silly lifecycle #~build: Args: [ '/d /s /c', 'jade -P -H src -o dst' ]
12 silly lifecycle #~build: Returned: code: 1 signal: null
info lifecycle #~build: Failed to exec build script
verbose stack Error: # build: `jade -P -H src -o dst`
verbose stack Exit status 1
verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
verbose stack at emitTwo (events.js:106:13)
verbose stack at EventEmitter.emit (events.js:191:7)
verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
verbose stack at emitTwo (events.js:106:13)
verbose stack at ChildProcess.emit (events.js:191:7)
verbose stack at maybeClose (internal/child_process.js:877:16)
verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
error Windows_NT 6.1.7601
error argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
error node v6.9.1
error npm v3.10.8
error code ELIFECYCLE
error # build: `jade -P -H src -o dst`
error Exit status 1
error Failed at the # build script 'jade -P -H src -o dst'.
error Make sure you have the latest version of node.js and npm installed.
error If you do, this is most likely a problem with the package,
error not with npm itself.
error Tell the author that this fails on your system:
error jade -P -H src -o dst
error You can get information on how to open an issue for this project with:
error npm bugs
error Or if that isn't available, you can get their info via:
error npm owner ls
error There is likely additional logging output above.
verbose exit [ 1, true ]
If -H is excluded everything runs fine. What seems to be the problem?
npm version: 6.9.1
jade version: 1.11.0
Issue has been resolved. My mistake was that I thought jade-cli was part of common jade package. Appears that you have to install it separately using
npm i jade-cli -g
-g for installing it globally.
After this compilation goes successfully and creates all necessary folder architecture