Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Install fails (maximum callstack exceeded)

See original GitHub issue

Hi,

I previously had file-icons installed but the package broke when trying to upgrade to file-icons@2.1.35, removing/reinstalling doesn’t fix the issue.

This is the output from apm install file-icons

Installing file-icons to /home/me/.atom/packages /usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:194
    if (this instanceof ReadStream)
             ^

RangeError: Maximum call stack size exceeded
    at Function.[Symbol.hasInstance] (<anonymous>)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:194:14)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)
    at ReadStream (/usr/lib/node_modules/atom-package-manager/node_modules/graceful-fs/graceful-fs.js:195:28)

I’m using Node 11.15.0.

Issue Analytics

State:
Created 4 years ago
Reactions:1
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

nerdymancommented, Aug 22, 2019

OK cool I’ll take a look at the APM issues, thanks for the quick response!

0reactions

nerdymancommented, Aug 23, 2019

Yep, my bad, I’m using Arch too. Arch’s Atom has been flagged as out of date, it’s still on 1.39.1-1. https://www.archlinux.org/packages/community/x86_64/atom/

Top Results From Across the Web

How to fix npm maximum call stack size exceeded error

Sometimes, you may see the npm maximum call stack size exceeded error when you run the npm install command: npm ERR! Maximum call...

Maximum call stack size exceeded on npm install

First of all you need to make sure that your node and npm versions are up to date. · Delete your node_modules folder...

Npm install maximum call stack size exceeded ?? - Laracasts

I installed fresh laravel 5.7. and tried to npm install.. it gives following error log 3264 verbose stack RangeError: Maximum call stack size...

Error on global install: Maximum call stack size exceeded #3749

Run sudo npm i -g @vue/cli inside Ubuntu's terminal. Observe the Maximum call stack size exceeded error. What is expected? vue-cli v3.5.5 should ......

JavaScript RangeError: Maximum Call Stack Size Exceeded

The RangeError: Maximum call stack size exceeded is thrown when a function call is made that exceeds the call stack size. This can...