Open namenotrequired opened 1 year ago
This bug happens only when running meteor --production but I'm not sure it happens on actual build/deploy. I stumbled upon it while looking for another bug. But I figured you'd want to know
meteor --production
Steps to reproduce:
$ meteor create reproduce --blaze $ cd reproduce $ meteor remove standard-minifier-js $ meteor add zodern:standard-minifier-js $ meteor add montiapm:agent $ meteor --production
Or replace montiapm:agent with montiapm:profiler for the same result
montiapm:agent
montiapm:profiler
client/main.js
console.log()
Result: the browser refreshes to a blank page, with an error in the console that it failed to fetch the javascript
I've seen this issue too. The build on disk seems correct, but the running app returns a 404 for the new js file.
This bug happens only when running
meteor --production
but I'm not sure it happens on actual build/deploy. I stumbled upon it while looking for another bug. But I figured you'd want to knowSteps to reproduce:
Or replace
montiapm:agent
withmontiapm:profiler
for the same resultclient/main.js
e.g. to add aconsole.log()
statement somewhere (but make sure it's a new hash)Result: the browser refreshes to a blank page, with an error in the console that it failed to fetch the javascript