WebAppInternals.setBundledJsCssPrefix and legacy build

I was using WebAppInternals.setBundledJsCssPrefix to setup some cloudfront, with static file stored in s3.
The reason for not using origin pull was to avoid cache problem.
Our files are uploaded to s3 with timestamped prefix.

I recently migrated one project to meteor 1.7 and noticed the build would force certain older devices to pull main js file from the web.browser.legacy instead.

at this point, it feels that setBundledJsCssPrefix is a little broken, because it doesn’t provide anyway to redirect the prefix based on the arch, it always pull from the root of whatever you define in setBundledJsCssPrefix.

would love to do a pr to fix this but i can’t wrap around the web_server.js right now.

so I’m wondering if there is a known workaround other than switching cloudfront to origin pull, or am I missing something?

1 Like

This sounds serious, have you created an issue on the Meteor repo?

1 Like