RangeError: Maximum call stack size exceeded

[flipps-dev]

Hello everyone, I'm struggling with this error. After the meteor installation on windows 10 I wanted to try if it worked, but when I type in the terminal meteor --version I get this error:

C:\Users\Users\AppData\Local\.meteor\packages\meteor-tool\1.6.1\mt-os.windows.x86_64\tools\fs\files.js:59 var useParsedSourceMap = function (pathForSourceMap) { ^ RangeError: Maximum call stack size exceeded

I thought the issue is in the file.js, but I don't know how I can fix it.

[abernix]

Please see #7896 (comment), which I believe is a duplicate of this issue. Other developers have reported success by moving other (higher up in the directory structure) node_modules out of the way.

If you could go through the same steps of moving other node_modules directories out of the way, but saving them, I'd certainly be interested in knowing exactly which turned out to be the offender. Perhaps it's the case that we need to change the meteor-tool itself (not for apps) to not use the same default module resolution paths. Though the fact that this is happening still leads me to believe that something else is slightly awry. Unfortunately, I haven't been able to put my finger on it yet (or reproduce it myself).

[flipps-dev]

A question,does it have to be a meteor folder inside %AppData%\Roaming\npm\node_module?

[abernix]

No, however that could be a problematic directory so I'd recommend temporarily renaming it to anything besides node_modules temporarily in order to eliminate it as a possibility. Additionally, any of the directories listed in the output of meteor node -p "modules.paths", when run from your app directory, could be a problem. The full plan for resolving modules, is quite complicated, but hopefully you'll find something quickly in the places I've suggested.

[flipps-dev]

It works yeah! I had another node_modules folder at C:\Users\UserName\node_modules I renamed this one to node_modules_old and created another one named node_modules. Maybe this last step is not important, maybe i had just renamed the old node_modules folder, without ctreate a new one, But now meteor works! Thank you!

[abernix]

Can you give me some idea of what was inside that node_modules directory (now node_modules_old)? If possible, a ZIP-file of its contents might be helpful in developing a fix for it! This isn't the first time this has affected a developer, and it's likely worth investigating a better solution.

[flipps-dev]

Of course, how can I reach you out?

[abernix]

If you think it could contain sensitive information (it shouldn't), you can private message me on the Meteor forums. I'm also abernix on there.

Perhaps a link to the ZIP on a Dropbox-like service?

[flipps-dev]

node_modules_old.zip

[abernix]

I can't be sure I'll get to this right away (esp. as it'll likely wait until I'm on Windows again) but thank you for providing that artifact. It could be very helpful to resolving this issue!

[juho]

FWIW we encounter this when deploying on Linux, solved with the environment variable

export NODE_OPTIONS=--max_old_space_size=4096

There's some discussion about it on the forums here: https://forums.meteor.com/t/how-to-increase-decrease-node-js-memory-limits-using-meteor/34355

[hwillson]

Since this issue was resolved in #9586 (comment) (and can also be addressed by increasing max_old_space_size as mentioned in #9586 (comment)), I'll close it for now. If for some reason this issue becomes more popular, we'll definitely re-open and investigate further. Thanks!

[yehudahkay]

Hi I'm having this issue as well, can't really use meteor, I tried installing on windows 10 and get

C:\node_modules\source-map-support\source-map-support.js:51
return function(arg) {
^

RangeError: Maximum call stack size exceeded

I have also npm installed previously but changing the name of node_modules didn't help

[yehudahkay]

I changed the name of C:\node_modules and it worked, but is very slow compared to a mac i tested it on. I tried installing on windows subsystem for linux but it is even slower. I use other packages on windows like git, npm, exp and ionic and they all work in git bash i don't need to open a windows cmd, and they also never had any conflicts. If meteor could work automatically in that fashion it would be great.

[simhadri-g]

Hi there, was having the same issue changing the name of c:\user\userName\node_modules to something else solved my problem.
Thanks.

[durjoy28]

I just installed meteor 1.8 in my win.10 pc by using choco but when I'm going to open a new project it's throw error;
^

RangeError: Maximum call stack size exceeded
why the error is generated?

[durjoy28]

[yehudahkay]

@durjoy28 try the solutions we posted, but if you have a mac i found meteor was designed more for mac...

[durjoy28]

@yehudahkay I've no mac but right now I need the meteor. I tried by changing node modules name but it not working. Please let me know what should I do?

[yehudahkay]

Im sorry I cant help any more, you can actually run a mac virtual machine on windows also. Search for the issue there are a lot of recommended solutions.

[durjoy28]

My problem is solved. Just, I changed my another node_modules folder C:\Users\Durjoy\node_modules_old previously it was C:\Users\Durjoy\node_modules. I shared for others as if they can solve easily when they will face the same problem.

[nja12]

This solution worked for me too, thanks all.

[preyasha2810]

@durjoy28 hello! have u solved the error???

[durjoy28]

Dear sir, still problem is appear. Available solution is not working for me.

…

On Tue, Feb 26, 2019 at 9:22 PM preyasha2810 ***@***.***> wrote: @durjoy28 <https://github.com/durjoy28> hello! have u solved the error??? [image: image] <https://user-images.githubusercontent.com/45910402/53423884-354e8b00-3a08-11e9-9e55-722381349bd8.png> — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#9586 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ATuxWa54LzlpaNva1STqqIK6r2Ukb_E6ks5vRVFIgaJpZM4RvaiM> .

[edemaine]

I just ran into this issue, unaware that I'd accidentally made a C:\Users\myusername\node_modules folder, and surprised that that stopped meteor from successfully running (in a different directory, C:\Users\myusername\Projects\myprojectname). The fix works, but presumably there's an underlying issue that causes this to happen? Can we fix it, instead of everyone needing to find this thread and delete/rename that folder?

[zodern]

There is an open issue for the cause: #10930 (comment). It should be fixed once #11740 is merged and the Windows build machine is updated to publish the meteor-tool with working symlinks.

[LizhenQiao]

I just ran into this issue, unaware that I'd accidentally made a C:\Users\myusername\node_modules folder, and surprised that that stopped meteor from successfully running (in a different directory, C:\Users\myusername\Projects\myprojectname). The fix works, but presumably there's an underlying issue that causes this to happen? Can we fix it, instead of everyone needing to find this thread and delete/rename that folder?

Vote for the idea. I was new to a meteor project and run into this issue. Though it is simple to change the folder name. It still took me several hours to find this solution. And to be honest, I believe it will prevent a great number of users who have the interest to get involved in meteor project. BTW, the solution itself seems uncomfortable. It is not the best idea for me to change the default folder name. (