How to prevent web.browser.legacy from being built with meteor build?

help
1

The --exclude-archs arg is not available for meteor build. And I see bundle/programs/web.browser.legacy in the final output.

I tried modifying .meteor/platforms to

server
browser

and

server
browser
modern

with no luck.

Also adding modern causes web.cordova to appear, which I don’t need. I just need web.browser (and the server to serve it), only as a web app for modern browsers.

This is more difficult to control than I imagine it should be, and it isn’t obvious how to control it. How can this be improved?

2

Which Meteor version are you using?

I just tested this on Meteor 3.4-rc.3 since I am using the latest version, and it works here. It should also work on 3.3 where this was introduced, and nothing related changed in 3.4. I will test again to be sure.

My .meteor/platforms looks like this (docs):

server
browser
modern

I have meteor.modern=true at package.json as well.

image

As you can see I don’t see either web.browser.legacy or web.cordova in my built app.

Have you tried running meteor reset first? It could be a stale cache issue in .meteor/local.

If the issue persist, could you try to reproduce it in a small sharable example? It may be an edge case I’m not aware with.

3

Ah ok this app is currently on 3.1.2.

I’m currently having this other issue that where Node.js version being older on Galaxy than locally causes me some errors.

I do need to update Meteor, but if Galaxy can run the same version of Node I should be fine for now (really trying to get stuff running for an event today)

4

I updated to 3.4-rc.3 locally, and I had to ensure jQuery was in pkg.json dependencies, and then I get this one error:

Screenshot 2026-01-13 at 4.03.19 AM
Screenshot 2026-01-13 at 4.03.19 AM2214×110 21.2 KB

but the app is working (login form style is a bit broken, but I can live with that for now).

Gonna see if this affects the npm version in deployment.

5

Off-topic from original post

Mmm, we introduced a breaking visual change on 3.4 for login form. Accounts UI CSS upgrade by StorytellerCZ · Pull Request #13840 · meteor/meteor · GitHub @storyteller do you get this error? It seems related on added imports on that PR. May It need a meteor reset for proper new changes on the Meteor accounts-ui package to take effect?

To avoid that error/visual breaking change, it may be better to be on Meteor 3.3.1.