Hmm interesting, I don’t understand how this would affect RAM, but I’ll try it out.
I am definitely going to do some investigating because this is a little weird, I’m hoping its just some weird setting I missed.
Edit:
Following those steps seems to have resolved it
I just added
global.webpack_public_path = Meteor.absoluteUrl();
to the start of my server code
I additionally added this to the config from what my AI suggested
…(Meteor.isProduction && {
devtool: false,
optimization: {
// Minification is the default in production, but being explicit avoids
// any Meteor integration override.
minimize: true,
// Tree-shake exports that are demonstrably unused at build time.
usedExports: true,
// Honor package.json sideEffects: false declarations to drop entire
// modules that have no live exports, reducing bundle (and heap) size.
sideEffects: true,
// Scope hoisting: merge small ES-module chains into a single function
// scope, cutting down the number of module-wrapper closures and the
// size of the webpack_require module registry at runtime.
concatenateModules: true,
},
}),
But I think that is all no-ops, so probably wasn’t relevant