-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Combine efforts with TraceKit? #45
Comments
Awesome, thanks for reaching out :) I'm going to respond to this via email unless you have any objections. |
Could you cc me as well? |
Hey guys, any comments on this subject? |
@ergo As soon as something, if anything, is decided, we'll let everyone know here and other places :) |
so 8 months have passed any news on this? |
I recently left my job and am looking at various things I could spend my time on and javascript error stuff is pretty high on the list. However, I'm currently in the position of not really want to do stack normalization on the client, if at all. The browsers give the errors they do. The stack normalization module could be loaded into the client, but I personally think server side data normalization is superior. |
I'm writing a JS client for http://errormator.com, and I have to normalize data for the api ;-) Thats why i'm bringing this up. |
ok, fork this repo and make it happen! You can even fork it into ErrorMator's GH account so the company can rep it |
@devinrhode2 any chance i can see you somewhere on freenode IRC if i have a question on the subject? |
Not usually on irc, but definitely add me on Google chat/hangouts,
|
Also, on v8 there's api's for controlling how many stack frames are
|
I respond pretty quickly via email too as you can sey
|
Did anything ever come out of this? |
Not really, unfortunately. The most recent work I know of this is here: Now that we can write ES6 thanks to Babel, many things can be done -Devin http://zerply.com/DevinRhode2 On Fri, May 1, 2015 at 7:30 PM, Blake Niemyjski notifications@github.com
|
Might be of interest, https://github.com/occ/TraceKit
I've been doing plenty of work on the project, along with @occ
TraceKit supports IE. (to the extent possible)
When we combine efforts, we just get more collective bug fixes and features. Both projects basically do the same thing, so I think it makes sense to do this eventually.
The text was updated successfully, but these errors were encountered: