Thanks! Despite the fact that we all come from heavy client side rendering backgrounds, you'll find the bulk of our UI is server side rendered :) Re: compilation errors - It depends on where our script is concatenated…
Thanks! The idea came from the fact that even when you do get a stack trace from a javascript error, it wasn't always that helpful :)
We went back and forth on this. We orginally just had /current/tracker.js but lots of folks feel weird about running potentially changing scripts on their production sites :) in the end we decided it was probably best…
We are working on getting it back up ASAP, in the meantime you can also check out http://trackjs.com which is just static files. (The blog is of course wordpress) (Edit: After kicking MySql things should be back - also,…
Eric from TrackJs here. 1) The performance impact should be functionally negligible. We do instrument a few of the lower level base JS objects but it's all very lightweight. We have not noticed any performance issues…
Thanks! Despite the fact that we all come from heavy client side rendering backgrounds, you'll find the bulk of our UI is server side rendered :) Re: compilation errors - It depends on where our script is concatenated…
Thanks! The idea came from the fact that even when you do get a stack trace from a javascript error, it wasn't always that helpful :)
We went back and forth on this. We orginally just had /current/tracker.js but lots of folks feel weird about running potentially changing scripts on their production sites :) in the end we decided it was probably best…
We are working on getting it back up ASAP, in the meantime you can also check out http://trackjs.com which is just static files. (The blog is of course wordpress) (Edit: After kicking MySql things should be back - also,…
Eric from TrackJs here. 1) The performance impact should be functionally negligible. We do instrument a few of the lower level base JS objects but it's all very lightweight. We have not noticed any performance issues…