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
A lame alternative is to set a breakpoint in the browser where the error is generated, and reproduce it.
Might this be worth raising an issue with meteor, to check for the JSON response text starting with "Your application is crashing" in case JSON.parse failed?
The text was updated successfully, but these errors were encountered:
I would have thought if you are launching the server with nohup you should be writing the to a log file somewhere (he says but he doesn't actually do it himself).
At https://github.com/oortcloud/unofficial-meteor-faq/blob/master/README.md#uncaught-syntaxerror-unexpected-token-y, if you've launched the server with nohup, and the terminal connection was lost how do you tap into its console output?
A lame alternative is to set a breakpoint in the browser where the error is generated, and reproduce it.
Might this be worth raising an issue with meteor, to check for the JSON response text starting with "Your application is crashing" in case
JSON.parse
failed?The text was updated successfully, but these errors were encountered: