hi there… we’re using Cursor… one issue, is that Cursor likes to change a files quickly - ge change/fix/change/fix. This causes tons of local meteor rebuilds / excessive hot reload… which absolutely smashes the local machine.
What’s the best approach here? Should I be using METEOR_DISABLE_OPTIMISTIC_CACHING=1?
Any other thoughts/recommendations pls?
This env var is for production builds/deploys not for HMR. If you wanted to disable HMR you need to comment out (or remove) this meteor package hot-module-replacement in your packages file.
In Webstorm I have an option to control how AI assist does things. In Chat I get the answer and apply them myself or copy-paste and with the AI agent for coding (Junie) I have this Brave option to let it do the changes without my intervention.
Do you have similar options in Cursor?
Another thing, you might be able to add to the AI configuration and add something like update the files but do not save. It is the saving (at least in Westorm) when the HMR kicks in.
oh wait… I see Environment Variables | Docs is only for production this issue related to development only
Thanks Paul,
Also, not only is the setting different… but I just noticed Environment Variables | Docs is only for production and this is a dev issue.
Actually I will try removing the package hot-module-replacement thanks.
Update: mmm… I don’t have hot-module-replacement in my package file… .is it on by default? is there another way to disable?
A Meteor package not an NPM one. You find it in your_app/.meteor/packages
yep… .I looked in there, it’s not there.
update: this proj has been going a while 
upgraded from Meteor v 1 → 2 ->3
I understand the HMR is done by Curson and not by Meteor.
“Disable Auto-Apply of Changes: Cursor AI IDE tends to auto-apply code changes without confirmation, which can be frustrating. Although there’s no explicit official toggle mentioned, some users report seeking options to disable this auto-apply behavior in Cursor’s settings or preferences. If you find such a setting, turning it off should make the AI wait for your confirmation before applying changes”
“Workarounds in Other Environments (like Visual Studio): For hot reload in Visual Studio, users can disable automatic rebuild on hot reload and choose to trigger it manually. This behavior may have parallels in Cursor, but direct config specifics are less documented”
Isn’t it better to stop the app, apply AI, then restart the apps to see the changes? What justifies having the app started and see intermediate changes on the app from continuous AI updates?
Alternatively, switch the watcher to polling and increase the interval by setting METEOR_WATCH_FORCE_POLLING and METEOR_WATCH_POLLING_INTERVAL_MS. These variables work in Meteor 3.3 with the new watcher and in the legacy watcher. But you get a downgrade on the watcher when you truly need reload speed.
Thanks.
yep, that’s what I have been doing - but a real pain, slows down dev… in short when you’re using a tool like Cursor you want to be able to mix AI and human in the loop… .having to stop/start the Meteor server is not what I’d call an optimal experience
We’re on 3.3… can you please explain those 2 params a bit more… ie what settings /interval would I want?
