You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
_1 Upvote_ When a client file changes, a rebuild happens, and eventually the client will be restarted.
But, if we change another client file while a build is in progress (the client is yet to be restarted) then that will trigger another build that queues up another client restart.
Idea: when a file changes during a build, cancel the following restart and only restart a single time once files have stopped changing; similar to how _.debounce works.
I find myself editing multiple files and saving them in succession, which causes multiple restarts. A single restart would be more efficient. The timeout of the "debounce" can just be the amount of time it takes for a rebuild to complete.
The text was updated successfully, but these errors were encountered:
stubailo
changed the title
[idea] Prevent client restarts when files change during build.
Restart build immediately if a file changes while the app is building
Aug 11, 2015
Thanks for the feature request! We welcome discussions about how to make Meteor better. If you haven't yet, check out our wiki page about feature requests on GitHub.
To help provide a more clear separation between feature requests and bugs, and to help clean up the feature request backlog, Meteor feature requests are now being managed under the https://github.com/meteor/meteor-feature-requests repository.
This feature request will be closed here, but anyone interested in migrating this feature request to the new repository (to make sure it stays active), can click here to start the feature request migration process. This manual migration process is intended to help identify which of the older feature requests are still considered to be of value to the community. Thanks!
_1 Upvote_ When a client file changes, a rebuild happens, and eventually the client will be restarted.
But, if we change another client file while a build is in progress (the client is yet to be restarted) then that will trigger another build that queues up another client restart.
Idea: when a file changes during a build, cancel the following restart and only restart a single time once files have stopped changing; similar to how
_.debounce
works.I find myself editing multiple files and saving them in succession, which causes multiple restarts. A single restart would be more efficient. The timeout of the "debounce" can just be the amount of time it takes for a rebuild to complete.
The text was updated successfully, but these errors were encountered: