Meteor 1.9 / 1.8.2 + Nexe not working anymore

Hey there,

we did an update from Meteor 1.8.1 to 1.9 and now we cannot start our app anymore if we package it with Nexe. There must have been changes from version 1.8.2 onwards that are responsible for breaking something in the Nexe utility. The error looks like this:

…\dist\programs\server\mini-files.js:1*
module.export({*
^*

TypeError: module.export is not a function

  • at Object. (…\output\dist\programs\server\mini-files.js:1:14)*
  • at Module._compile (internal/modules/cjs/loader.js:959:30)*
  • at Object.Module._extensions…js (internal/modules/cjs/loader.js:995:10)*
  • at Module.load (internal/modules/cjs/loader.js:815:32)*
  • at Function.Module._load (internal/modules/cjs/loader.js:727:14)*
  • at Module.require (internal/modules/cjs/loader.js:852:19)*
  • at require (internal/modules/cjs/helpers.js:74:18)*
  • at Object. (…\output\dist\programs\server\boot.js:14:15)*
  • at Object. (…\output\dist\programs\server\boot.js:466:3)*
  • at Module._compile (internal/modules/cjs/loader.js:959:30)*

Do you have any ideas how to fix that?

rka

My first thought is that nexe might have built with the wrong node version as a target?
I’ve never used nexe before so not sure

Check the breaking changes in 1.8.2. There is a note about the use of export and the error seems related

2 Likes

Yes, we recognized the changes but we were not able to solve this issue. It seems to be too much “magic” which is done by tools like reify compiler. This breaks our packaging with Nexe.

We also tried zeit/pkg but it’s even more difficult to combine it with Meteor.

We are not sure if we can continue like that with Meteor. We are frozen at 1.8.1 at the moment. Apparently our setup is not so widespread. We deploy our software only to servers in local networks and therefore need to package it. :neutral_face: