My meteor app runs on v1.5.2 and works great.
Upgraded to v188.8.131.52, still works great locally (macos) but deployed version is throwing an error. Deployment is via aws elastic beanstalk. The ec2 environment logs show that the app is throwing this error:
> node main.js /var/app/current/programs/server/boot.js:392 }).run(); ^ Error: Cannot find module "fibers/future" at Object.require (/var/app/current/programs/server/boot.js:232:24) at packages/meteor.js:93:20 at packages/meteor.js:263:4 at packages/meteor.js:1392:3 at /var/app/current/programs/server/boot.js:339:34 at Function._.each._.forEach (/var/app/current/node_modules/underscore/underscore.js:153:9) at /var/app/current/programs/server/boot.js:158:5 at /var/app/current/programs/server/boot.js:388:5 at Function.run (/var/app/current/programs/server/profile.js:510:12) at /var/app/current/programs/server/boot.js:387:11
What could have caused that, solutions, ideas?
For reference, some interesting facts which may be relevant:
my package.json has:
my build script is running (among other commands):
meteor yarn install meteor build --directory [my app's dir] --architecture os.linux.x86_64 zip ... # creating bundle
I run the build script on both macos and Linux.
When deploying the resulting bundle to beanstalk before the v184.108.40.206 (also before v220.127.116.11 ) update, the app started successfully. The update definitely broke it
I am aware there’s a shitstorm involving
bcrypt binaries, but app does not include it, so this option gets ruled out…
Could this issue be one of em issues which result from missing the target architecture binary of fibers/future? If so, I have to wonder how does
meteor yarn install handle those things. After all, I’m not providing the architecture in the yarn command.
Also, not sure if this matters; a while back ago my app was running on an older meteor version (~v1.1). Since then, I’ve been bumping it up regularly up to v1.5.2. I wonder if there’s anything under
.meteor/packages which may be breaking
fibers/future. At 1st glance, no obvious culprits…