I'm getting an error when I run npm install -g aws-cdk it says Maximum call stack size exceeded if I don't do the global install then I don't get that error but my windows machine doesn't pick up that I have AWS-CDK installed then. The documentation also says to install globally.
Has anyone encountered this?
An important note I am using a company PC that sits behind a VPN. I can't however disconnect this from the VPN.
I'm running version 16.18.0 node and version 8.19.2 of npm
The log file where the error is:
37 verbose stack at resolve (node:path:158:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:21:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)
37 verbose stack at realpathCached (C:\Program Files\nodejs\node_modules\npm\node_modules\#npmcli\arborist\lib\realpath.js:41:10)```
I had the same issue. My problem is that I work on a PC with roaming profiles where APPDATA is redirected to a server share. In my case changing the npm prefix directory solved the issue. Try the following:
npm config --global get prefix
In my case the output was: \\SRV02\Profiles\USERNAME_HERE\AppData\Roaming\npm
I changed it using the following command
npm config --global set prefix C:\tools\npm-prefix
then everything works. Remember to add C:\tools\npm-prefix to the PATH environment variable
This may be related to something in your global node_modules directory and not the AWS CDK. Try some answers to this question first.
Related
Trying to build a dev version of an APK (Android) but I keep getting the following error.
14572 timing reify:rollback:createSparse Completed in 5948ms
14573 timing reify:rollback:retireShallow Completed in 14ms
14574 timing command:install Completed in 278406ms
14575 verbose stack Error: command failed
14575 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/#npmcli/promise-spawn/lib/index.js:63:27)
14575 verbose stack at ChildProcess.emit (node:events:527:28)
14575 verbose stack at maybeClose (node:internal/child_process:1092:16)
14575 verbose stack at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
14576 verbose pkgid #expo/html-elements#0.0.2
14577 verbose cwd /Users/faisaliqbal/.turtle/workingdir/android/sdk42
14578 verbose Darwin 21.3.0
14579 verbose node v16.15.1
14580 verbose npm v8.11.0
14581 error code 1
14582 error path /Users/faisaliqbal/.turtle/workingdir/android/sdk42/packages/html-elements
14583 error command failed
14584 error command sh -c expo-module prepare
14585 error /Users/faisaliqbal/.turtle/workingdir/android/sdk42/node_modules/commander/index.js:837
14585 error throw new Error(executableMissing);
14585 error ^
14585 error
14585 error Error: 'expo-module-prepare' does not exist
14585 error - if 'prepare' is not meant to be an executable command, remove description parameter from '.command()' and use '.description()' instead
14585 error - if the default executable name is not suitable, use the executableFile option to supply a custom name
14585 error at ChildProcess.<anonymous> (/Users/faisaliqbal/.turtle/workingdir/android/sdk42/node_modules/commander/index.js:837:15)
14585 error at ChildProcess.emit (node:events:527:28)
14585 error at Process.ChildProcess._handle.onexit (node:internal/child_process:289:12)
14585 error at onErrorNT (node:internal/child_process:478:16)
14585 error at processTicksAndRejections (node:internal/process/task_queues:83:21)
14586 verbose exit 1
14587 timing npm Completed in 278532ms
14588 verbose unfinished npm timer reify 1656882423113
Here are the versions of the app I am using.
Note: This project is working and compiling fine on another machine.
OS - darwin 12.2.1 (Monterey)
turtle - 0.27.4
Java (2) Versions:
java 18.0.1.1 2022-04-22
openjdk 11.0.15 2022-04-19
expo - 5.4.12
nodejs - v16.15.1
npm - 8.11.0
setup:android is all good
setup:ios is all good
IPA (IOS Binary) compiles without any issue.
Command to start the build:
turtle build:android \
--keystore-path ./keystore/keystore_android.jks \
--keystore-alias "store (redacted)" \
--allow-non-https-public-url \
--gradle-args "--warning-mode all" \
--public-url expo_url (redacted) \
-t apk
What might be the causing this?
Downgrading NodeJS version from 16 to 14 helped.
I originally installed NodeJS using official installer and after removing the installed version I reinstalled node using brew:
brew install node#14
(everything else I specified in my question was left untouched.
I try create a react-app with npx create-native init project but the react version was 17.0.2.
I used npm install react react-dom( following https://reactjs.org/blog/2022/03/08/react-18-upgrade-guide.html) to update for the new version but now I received the message when I try create a nem project: npm ERR! could not determine executable to run.
What should I do?
log:
38 verbose stack Error: could not determine executable to run
38 verbose stack at getBinFromManifest (C:\Users\55319\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\get-bin-from-manifest.js:17:23)
38 verbose stack at exec (C:\Users\55319\AppData\Roaming\npm\node_modules\npm\node_modules\libnpmexec\lib\index.js:135:15)
38 verbose stack at async module.exports (C:\Users\55319\AppData\Roaming\npm\node_modules\npm\lib\cli.js:78:5)
39 verbose pkgid create-native#1.0.0
40 verbose cwd C:\Users\55319
41 verbose Windows_NT 10.0.19044
42 verbose node v16.15.0
43 verbose npm v8.8.0
44 error could not determine executable to run
45 verbose exit 1
46 timing npm Completed in 2369ms
47 verbose code 1
48 error A complete log of this run can be found in:
48 error C:\Users\55319\AppData\Local\npm-cache_logs\2022-05-12T01_59_05_028Z-debug-0.log
CMD
It installed that version because that's the version it's compatible with, as of this writing (RN 68.1). React Native often doesn't use the latest version of React. If you open up the changelog for React Native and search for React 17, you'll see it was introduced into React Native version 64.0. There are no hits for React 18 because it hasn't yet been integrated.
I'm having a very strange issue with nvm, npm and webpack.
We have a webpack file with a npm run publish command. I have 4 stacks setup locally on the same code repository. In 3 of the stacks, I can npm run publish without an issue. However, in the 4th stack I always get a sh: 1: webpack: not found error when I run the command. The worrisome bit, is the codebases are identical. I've ran diffs, altered permissions, ran npm rebuild, re-ran npm install and nvm use. I've removed the node_modules directory and ran an npm install. No matter what I do, I get the same error.
Here is the verbose error with a few local names blocked out:
21 timing command:run-script Completed in 25ms
22 verbose stack Error: command failed
22 verbose stack at ChildProcess.proc.on (/home/<usr>/.nvm/versions/node/v11.14.0/lib/node_modules/npm/node_modules/#npmcli/promise-spawn/index.js:64:27)
22 verbose stack at ChildProcess.emit (events.js:193:13)
22 verbose stack at maybeClose (internal/child_process.js:999:16)
22 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:266:5)
Any help is very much appreciated! Thanks!
I ended up resolving it by copying over the node_modules directory from one of the working codebases. Not entirely sure what the problem was though.
I'm running Windows 10, NPM v5.5.1, and node v8.9.1.
Edit: I have since updated to node v8.9.4 and npm v5.6.0. The problem remains unchanged.
I set up my development environment on this machine about 2 months ago. I'm using Angular CLI to build my client apps.
Everything was going fine. I added a few packages via NPM without a problem, such as Gulp and ngx-bootstrap. Then I started to run into errors on some of my package installs.
The errors are:
npm ERR! code PATH_LENGTH_EXCEEDED
npm ERR! errno PATH_LENGTH_EXCEEDED
npm ERR! request to https://registry/npmjs.org/{{package}} failed, reason: path length constraint exceeded
npm ERR! A complete log of this run can be found in:
npm ERR! {{npm_cache path}}\_logs\2018-02-08T14_43_40_856Z-debug.log
The contents of that log file are:
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 'install',
1 verbose cli 'ngx-cookie-service',
1 verbose cli '--save' ]
2 info using npm#5.5.1
3 info using node#v8.9.1
4 verbose npm-session d55be12849534a0a
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for ngx-cookie-service#latest request to https://registry.npmjs.org/ngx-cookie-service failed, reason: path length constraint exceeded
8 verbose type system
9 verbose stack FetchError: request to https://registry.npmjs.org/ngx-cookie-service failed, reason: path length constraint exceeded
9 verbose stack at ClientRequest.req.on.err (C:\Program Files\nodejs\node_modules\npm\node_modules\pacote\node_modules\make-fetch-happen\node_modules\node-fetch-npm\src\index.js:68:14)
9 verbose stack at emitOne (events.js:116:13)
9 verbose stack at ClientRequest.emit (events.js:211:7)
9 verbose stack at TLSSocket.socketErrorListener (_http_client.js:387:9)
9 verbose stack at emitOne (events.js:116:13)
9 verbose stack at TLSSocket.emit (events.js:211:7)
9 verbose stack at emitErrorNT (internal/streams/destroy.js:64:8)
9 verbose stack at _combinedTickCallback (internal/process/next_tick.js:138:11)
9 verbose stack at process._tickCallback (internal/process/next_tick.js:180:9)
10 verbose cwd C:\Development\test
11 verbose Windows_NT 10.0.15063
12 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "install" "ngx-cookie-service" "--save"
13 verbose node v8.9.1
14 verbose npm v5.5.1
15 error code PATH_LENGTH_EXCEEDED
16 error errno PATH_LENGTH_EXCEEDED
17 error request to https://registry.npmjs.org/ngx-cookie-service failed, reason: path length constraint exceeded
18 verbose exit [ 1, true ]
I researched this, and found the Windows 10 file path 260 character limitation. I thought that npm version 3.1.0 should have fixed this issue, but I decided to followed the instructions in this answer, because I'm still running into this issue despite using NPM v5.5.1.
I found that my version of Windows was prior to the roll out of the feature that lets you disable this limitation. I updated to Version 1703 (OS Build 15063.483), and to enable Win32 long paths.
Yet I'm still getting the error, and unable to install a variety of npm packages.
In testing to see if it was an issue with packages that have a lot of dependencies, I tried installing or reinstalling a couple of other packages.
Some fail with the errors above. Others succeed with the following warnings:
npm WARN Unexepcted warming for https://registry.npmjs.org/: Miscellaneous Warning PATH_LENGTH_EXCEEDED: request to https://registry.npmjs.org/{{package name}} failed, reason: path length constraint exceeded
npm WARN Using stale package data from https://registry.npmjs.org/ due to a request error during validation
Packages throwing the error include:
jslint
ngx-cookie-service
chart.js
angular-cli
Packages that throw the warnings include:
font-awesome
#angular/cli
moment
ngx-bootstrap
bootstrap
jasmine
I suspect that something has changed, either in a policy on my workstation, or in our network security, that is causing this. All of the packages that succeed seem to be packages that I had previously installed, either as a direct install, or as a dependency of #angular/cli (one of the first packages I installed). I'm assuming that the stale package data warning indicates that whatever problem I have with the path length is preventing updated data being retrieved, and therefore npm is falling back to cached data from previous installations of the selected package and its dependencies.
So now I'm stumped as to how to diagnose exactly where the issue is happening. If its a security policy that changed, then I need to be able to describe exactly what is being blocked so that I can work with our security department to fix this. But the only information I can find about the PATH_LENGTH_EXCEEDED errors lead me to old information about versions of npm prior to 3.1.0.
How can I identify the source of this problem?
After additional searching, I found references to path length exceeded with regards to SSL/TLS certificate authorities. I tested this issue by changing the npm registry to use http instead of https (note: this is a temporary step only; I have turned https back on once I verified the issue):
npm config set registry http://registry.npmjs.org/
This allowed me to install the problematic packages.
It seems the underlying cause is SSL Inspection performed by our network security team. The decryption, inspection, and re-encryption process, and subsequent changes in the Issuing Authority on the certificate, apparently triggers this error.
Running npm install and failed with error the following is from npm-debug.log file The same commands works yesterday. There's no change in package.json file.
15065 info install gulp-jsdoc#0.1.5
15066 info postinstall gulp-jsdoc#0.1.5
15067 verbose unlock done using /home/centos/.npm/_locks/gulp-jsdoc-a48e57f10f1c6755.lock for /data/jenkins/workspace/node_modules/gulp-jsdoc
15068 verbose stack Error: Invalid Package: expected taffydb but found taffydb-jsdoc
15068 verbose stack at /usr/lib/node_modules/npm/lib/cache/add-local-tarball.js:127:21
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:356:5
15068 verbose stack at checkBinReferences_ (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:320:45)
15068 verbose stack at final (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:354:3)
15068 verbose stack at then (/usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:124:5)
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/read-package-json/read-json.js:243:12
15068 verbose stack at /usr/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:78:16
15068 verbose stack at FSReqWrap.readFileAfterClose [as oncomplete] (fs.js:380:3)
15069 verbose cwd /data/jenkins/workspace/
15070 error Linux 3.10.0-327.18.2.el7.x86_64
15071 error argv "/usr/bin/node" "/usr/bin/npm" "install"
15072 error node v4.4.5
15073 error npm v2.15.5
15074 error Invalid Package: expected taffydb but found taffydb-jsdoc
15075 error If you need help, you may report this error at:
15075 error <https://github.com/npm/npm/issues>
15076 verbose exit [ 1, true ]
15077 verbose unbuild node_modules/jsdoc
15078 info preuninstall jsdoc#3.3.0-alpha5
15079 info uninstall jsdoc#3.3.0-alpha5
Thanks
G.S.
It would appear that this latest commit in the taffydb-jsdoc fork has broken it:
https://github.com/hegemonic/taffydb/commit/507d2d75fa16e1386f6d50abee1894b264d4458b
(https://www.npmjs.com/package/taffydb-jsdoc)
(Description updated)
The package has been renamed from taffydb to taffydb-jsdoc, so npm is finding a conflict between the expected and the declared package names. In our case and the OP's, hegemonic's fork of taffydb is being referenced by jsdoc, which is a node module required by gulp-jsdoc:
https://github.com/jsBoot/gulp-jsdoc/blob/v0.1.4/package.json#L39
https://github.com/jsdoc3/jsdoc/blob/v3.3.0-alpha5/package.json#L26
EDIT: The author of this fork has contacted me to say the issue has been resolved, as shown in this new commit (package name reverted):
https://github.com/hegemonic/taffydb/commit/e41b5e179e197bb85c5fb887b707672b1e5ca079
I can confirm that our npm install(s) are now working again.