Meteor 3.x exited with code 7

Hi Meteor Team and Community,

Thank you for your amazing work and consistent updates! My team and I are eager to upgrade to the latest version. We’re currently working on updating our large project from Meteor 2.16 to 3.1.1. However, after the update, we’re encountering issues with the build process.

After completing the update, I reset Meteor and the database. Our project also underwent an async refactor, meaning the codebase was adapted to use async methods and collection calls.

During the build process, I receive the following error:

=> Started proxy.
=> Started MongoDB.
=> Exited with code: 7
=> Your application is crashing. Waiting for file change.

–Verbose gives me

Adding CSS > Merging [ app/imports/ui/teacher/MaterialPage/ShareMaterial/_styles.scss ] > 1k
Adding CSS > Merging [ app/client/main.scss ] > 626k
minifyStdCSS: Total CSS 825k                 /
=> Exited with code: 7
=> Your application is crashing. Waiting for file change.

Additional Context:
I suspect the crash might be related to imports, possibly due to the new JavaScript strict mode introduced in Meteor 3.x. However, I’m unsure if this could lead to an exit code 7.

Could someone provide more details about what exit code 7 indicates? I couldn’t find information about it in the documentation or codebase.

Any insights or guidance would be greatly appreciated!

Thank you for your help.

Do you have a current SCSS processor such as the updated leonardoventurini:scss?

1 Like

yes i’m using leonardoventurini:scss but no specific version

meteor-base@1.5.2 # Packages every Meteor app needs to have
mobile-experience@1.1.2 # Packages for a great mobile UX
mongo@2.1.0 # The database Meteor supports right now
reactive-var@1.0.13 # Reactive variable for tracker

es5-shim@4.8.1 # ECMAScript 5 compatibility for older browsers
ecmascript@0.16.10 # Enable ECMAScript2015+ syntax in app code
shell-server@0.6.1 # Server-side component of the `meteor shell` command
accounts-password@3.0.3
universe:i18n
#fourseven:scss@4.17.0-rc.0 #replaced by leonardoventurini:scss

email@3.1.1
static-html@1.4.0
react-meteor-data@3.0.2
meteortesting:mocha
percolate:migrations

oauth@3.0.1 #external authprovider
oauth2@1.3.3 #oauth standart
accounts-oauth@1.4.6
http #post auth requests
fetch@0.1.5
service-configuration@1.3.5 #collection to keep our services save
standard-minifier-css@1.9.3
typescript@5.6.3
ddp-rate-limiter@1.2.2
standard-minifier-js@3.0.0
leonardoventurini:scss #replaces fourseven:scss@4.17.0-rc.0

ok, I noticed this (above). Can you try to comment out some SCSS imports and reduce the size and see if it moves on. That is a lot of SCSS if k refers to “KB”.

Installed Meteor libraries versions can be check in the versions file unde the .meteor folder.

It also crashes on < 200k.

same error or something different related to syntax or missing imports which possibly were not triggered in previous versions? (BTW I use leonardoventurini:scss@2.0.0 with Meteor 3.1.1)

yes it was the same error. I’m on leonardoventurini:scss@2.0.0 as well with 3.1.1 on my failing branch.

To be frank, at this point I don’t know if the build problem is related to SCSS or something else and it just stops with that message.
I would go and further remove SCSS imports until SCSS is excluded as a possible problem.
Maybe you could use the METEOR_PROFILE env variable and see if you get more info. Maybe experiment with different lengths of time for METEOR_PROFILE.

Another thing … If you still have old files/bundles in .meteor/local, built with other versions of Meteor you would rather delete everything under /local and only keep the DB.

Overall I would love to understand more about what causes code 7. In my experience this get’s thrown when something happens like server tries to import from client or something like this. Wondering why my current build works on 2.16 though.

Kind of having an error when attempting to throw an error :).
I might be hallucinating but I think @zodern might have had a recent comment about server should not crush due to errors in packages but … I also not sure that would be related to the present problem.

Thanks for additional information.

I was able to solve it. This little friend here caused the issue

What we see here is using a function from /imports/ui/whatever in imports/api/meteor/methods.ts

This is an import conflict but Meteor just throws “Exited with code: 7”

Overall this error was caused because of bad practice in code base. Detailed Error Logging from Meteor side would be very helpfull for those cases.

And I still would be very interested why is that a problem on Meteor3 and was not on Meteor 2 alrdy?

Has this something to do with StrictMode?