I’m running into a LOT of issues trying to run an open-source meteor application.
Currently, I’m getting the following:
E:\Code\node-on-fhir>meteor run
C:\Users\MYUSER\AppData\Local\.meteor\packages\meteor-tool\2.7.3\mt-os.windows.x86_64\dev_bundle\lib\node_modules\meteor-promise\promise_server.js:218
throw error;
^
RangeError: Maximum call stack size exceeded
(Use `node --trace-uncaught ...` to show where the exception was thrown)
I am on Windows 11, and was using Node.JS 16. I uninstalled and re-installed with v14.20.0.
The node-on-fhir project has a .meteor/release file that indicates version 2.7.1… When I run meteor run with 2.7.3 installed, it attempts to download 2.7.1 and then fails with a similar “Max call stack size exceeded”, but from a different file (files.js)
I updated the .meteor/release file to use 2.7.3, which matches my global install of meteor. It doesn’t attempt to download meteor-tools, but still results in a “Max call stack size exceeded”, as shown above.
When I do all of this on an ubuntu VM, it installs/runs without error. I’d really like to figure out why this is broken on my windows VM, though, as that’s my usual workstation.