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

Already on GitHub? Sign in to your account

maximum call stack error in `npm restart` #667

graphnode opened this Issue Mar 3, 2011 · 3 comments


None yet
2 participants
$ npm restart
npm info it worked if it ends with ok
npm info using npm@0.3.12
npm info using node@v0.4.1
npm ERR! RangeError: Maximum call stack size exceeded
npm ERR! Report this *entire* log at <http://github.com/isaacs/npm/issues>
npm ERR! or email it to <npm-@googlegroups.com>
npm ERR! Just tweeting a tiny part of the error will not be helpful.
npm ERR! System Linux
npm ERR! argv { remain: [],
npm ERR! argv   cooked: [ 'restart' ],
npm ERR! argv   original: [ 'restart' ] }
npm not ok

It would make sense to restart npm by default or at least warn the user about the lack of argument.


isaacs commented Mar 3, 2011

Since npm doens't have any start, stop, or restart scripts defined, it wouldn't make much sense to "restart npm".

When running without any arguments, it attempts to call these scripts on the package in the cwd. I'm guessing you ran this in a folder without a package.json file.

A better error is definitely required, but the behavior should be an error.


isaacs commented Mar 3, 2011

Closed by 2f87c6e Allow running any 'script' command in a package.json folder


isaacs commented Mar 3, 2011

On second thought, if there's a package.json file, then just do it right there in that local folder.

This issue was closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment