We’re on 3.3… can you please explain those 2 params a bit more… ie what settings /interval would I want?
These are just env variables. Use them as shown in the docs link above when running meteor run. I can’t say what exact values you’ll need, you’ll have to experiment to see what fits your setup. Keep in mind though: increasing the watcher interval won’t make updates show up faster. METEOR_WATCH_POLLING_INTERVAL_MS basically adds a debounce so file changes trigger only once per interval. That reduces load on Meteor’s core, but it won’t make reloads more responsive, and might even delay them.
Limitation being anything that ties into Meteor’s core build system. For example when developing an Atmosphere package or making modifications to a local Meteor package. Apart from that, application code and anything managed by npm or Node’s native module system is handled at lightning speeds
I think @jorgenvatle summed that up well. Meteor’s current bundler doesn’t handle reloads efficiently. Using a modern bundler like Meteor-Vite makes reloads much quicker, with faster rebuilds, HMR and no full server restarts frequently. All this happens by offloading app code compilation to a modern tool. Maybe try Meteor-Vite as a proof of concept and see how it performs for you.
Officially, we’re addressing this with Meteor-Rspack integration. Reloads there are much faster and less resource-heavy, which should improve the AI-driven code change workflow once that milestone lands. That’s our short-term path forward with modern tools. We’ll come back to this after the 3.4 beta is out so you can test it and share feedback.