Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CLI issue on everything #7092

Open
BrianStrout opened this issue Mar 6, 2025 · 15 comments
Open

CLI issue on everything #7092

BrianStrout opened this issue Mar 6, 2025 · 15 comments
Labels
status: missing info/reproduction type: bug code to address defects in shipped code

Comments

@BrianStrout
Copy link

Describe the bug

After installing netlify-cli, the only thing I can do is "netlify –help" everything else returns the following error:

RangeError: Maximum call stack size exceeded

this includes "netlify" "netlify init" etc.

Please help me with what/how to troubleshoot on my mac. Thanks!

Steps to reproduce

npm install netlify-cli -g
netlify init

Configuration

can't run anything even to start project

Environment

sh: envinfo: command not found

@BrianStrout BrianStrout added the type: bug code to address defects in shipped code label Mar 6, 2025
@BrianStrout
Copy link
Author

Some other useful info. I can install other npm fine. Ios is Sonoma version 14.4.

@dongwa
Copy link

dongwa commented Mar 8, 2025

+1

@abrahamguo
Copy link

Is any stack trace shown with the error?

@BrianStrout
Copy link
Author

BrianStrout commented Mar 8, 2025 via email

@dongwa
Copy link

dongwa commented Mar 10, 2025

no stack trace ,just netlify –help can work

Image

@IamAbhinav03
Copy link

Having the same issue! I can't trace the error as well. It's just giving Range Error: Maximum call stack size extended

@mgajowa
Copy link

mgajowa commented Mar 12, 2025

Same for me.

@amaccann
Copy link

amaccann commented Mar 14, 2025

Happening here too; any and all netlify xyz commands throwing the same error: tried installing both globally & locally within my specific project - same result. Every single command (except -h) throws the same RangeError.

FWIW, running Node v22.14.0 and installed ^19.0.2 of netlify-cli

@amaccann
Copy link

Tried installing 18.1.0 just to drop to last major version - same problem.

@overlordofmu
Copy link

I am unable to reproduce this error with the Node.js and Netlify CLI version reported. The bug form asks for the output of this command:

npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli

However, that output has not been provided by anyone on the issue. Would someone that is experiencing this error please provide the output of the command above?

I do see this provided in the original post:

sh: envinfo: command not found

That is an error and not the output of that command. You will need to install envinfo to resolve that error first. The output of that command is key to finding the root cause here.

@BrianStrout
Copy link
Author

OP here, running

npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli

gets me:

System:
OS: macOS 14.4
CPU: (14) arm64 Apple M3 Max
Memory: 663.08 MB / 36.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.13.1 - /usr/local/bin/node
npm: 11.2.0 - /usr/local/bin/npm
npmPackages:
netlify-cli: ^12.1.1 => 12.1.1
npmGlobalPackages:
netlify-cli: 19.0.2

The older netlify was installed trying to see if it was a recent version issue, and that version still runs on my other computer fine

@IamAbhinav03
Copy link

Running npx envinfo --system --binaries --npmPackages netlify-cli --npmGlobalPackages netlify-cli gives me

System:
OS: macOS 15.3.1
CPU: (8) arm64 Apple M1
Memory: 162.55 MB / 16.00 GB
Shell: 5.9 - /bin/zsh
Binaries:
Node: 22.2.0 - /usr/local/bin/node
Yarn: 1.22.22 - /usr/local/bin/yarn
npm: 10.8.1 - /usr/local/bin/npm
npmGlobalPackages:
netlify-cli: 19.0.2

@serhalp
Copy link
Collaborator

serhalp commented Mar 17, 2025

Has anyone with this issue been able to identify a prior version of netlify-cli that works? or any idea what changed before this started happening?

This is difficult to investigate as is! Anything you all can share might be useful. Thanks :)

@amaccann
Copy link

@serhalp I tried a very versions back and had the problem; finally installed 17.38.1 and it worked. It was an arbitrary pick.

@benjaminmbrown
Copy link

similar issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: missing info/reproduction type: bug code to address defects in shipped code
Projects
None yet
Development

No branches or pull requests

9 participants