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
{{ message }}
This repository has been archived by the owner on Jan 21, 2024. It is now read-only.
I don't like the idea of TraceKit making a request for my js file to provide lines of context when it's almost no different than just getting the straight line number of the error.
I'm proposing we remove all operations dealing with requesting a remote file and analyzing it.
But from what I understand, remote source fetching is a big component of TraceKit. It is what makes stacktraces work in IE, for example, which I think is actually very nifty.
Remote fetching is an important part of tracekit. I don't think removing it would be a good idea. I do support having/improving the "do not fetch" flag though.
I don't like the idea of TraceKit making a request for my js file to provide lines of context when it's almost no different than just getting the straight line number of the error.
I'm proposing we remove all operations dealing with requesting a remote file and analyzing it.
Related to #11, testing becomes tricky
The text was updated successfully, but these errors were encountered: