Meteor-feature-requests: Avoid rebuilding the app three times on error
Description
Since Meteor tries to restart the app three times when there is a development server runtime error, it takes longer time to read error logs, since they are published 3 times.
Suggestion
Make the count of restarts as an option or environment variable.
Details
This has been requested firstly in meteor/meteor#6481, but was closed and suggested to create a feature request.
vblagomir
All 4 comments
I like this idea, and I would even go further: instead of allowing the restart count to be configured, let's get rid of the multiple restart feature altogether. In more than four years working on Meteor, I have never once seen the second or third restart actually fix any problems.
benjamn
on 21 Oct 2018
Great that you like it! I have not seen the second or third restart actually fix any problem, but _maybe_ someone had.. :-)
vblagomir
on 21 Oct 2018
If you (or anyone) is interested in attempting a pull request, here's the relevant code. Of course you could just change that 3 to a 1, but ideally we could clean up any lingering multiple restart logic too.
benjamn
on 21 Oct 2018
This has been implemented in Meteor 1.9
StorytellerCZ
on 11 May 2021
Related issues
vladejs
路
6Comments
danrubins
路
3Comments
glasser
路
5Comments
trusktr
路
6Comments
datacarl
路
3Comments
Most helpful comment
I like this idea, and I would even go further: instead of allowing the restart count to be configured, let's get rid of the multiple restart feature altogether. In more than four years working on Meteor, I have never once seen the second or third restart actually fix any problems.