Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

npm ERR! cb() never called!Unhandled rejection RangeError: Maximum call stack size exceeded myProject #19567

Open
3 tasks
FE-xiaoJiang opened this issue Jan 10, 2018 · 3 comments
Labels

Comments

@FE-xiaoJiang
Copy link

I'm opening this issue because:

  • npm is producing an incorrect install.

What's going wrong?

Unhandled rejection RangeError: Maximum call stack size exceeded myProject
at RegExp.test ()
at /usr/local/lib/node_modules/npm/node_modules/aproba/index.js:38:16
at Array.forEach (native)
at module.exports (/usr/local/lib/node_modules/npm/node_modules/aproba/index.js:33:11)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:37:3)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
at flatNameFromTree (/usr/local/lib/node_modules/npm/lib/install/flatten-tree.js:39:14)
npm ERR! cb() never called!

How can the CLI team reproduce the problem?

npm i,then throw error

supporting information:

  • npm -v prints:5.3.0
  • node -v prints:v8.1.3
  • npm config get registry prints:https://registry.npmjs.org/
  • Windows, OS X/macOS, or Linux?:macOS
  • Network issues:
    • Geographic location where npm was run:
    • I don't use a proxy, but have limited or unreliable internet access.
  • Container:
    • I develop using Vagrant on OS X or Linux.
@kenany kenany added the npm5 label Jan 10, 2018
@wind-hx
Copy link

wind-hx commented Jan 13, 2018

Like you, I met the same problem. How do you solve it?

@jinjinwa
Copy link

+1

1 similar comment
@johnny1952
Copy link

+1

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

5 participants