Add comment to Raven.wrap so people stop blaming Raven.js

[benvinegar]

The idea is that this comment will appear in stack frames to help users understand what is happening, whereas right now they are just seeing this (screenshot below), which leads them to believe there is a bug in the library when it's really just normal operation:

Before:

After:

Making this change cause I'm getting tired of explaining it to people.

cc @getsentry/javascript

[MaxBittker]

🙌

[MaxBittker]

maybe mention that their error will be earlier in the stack trace?

[benvinegar]

maybe mention that their error will be earlier in the stack trace?

Not always. In this example, Raven is the only frame.

This "freed script" error means that a function existed (say, accessible via an iframe), then was removed from the page when the iframe was removed. The function is still attempted to be executed asynchronously via something like setTimeout(freedFn, 10000) – and because setTimeout is async, Raven is the only frame (wraps freedFn in a try/catch).

[benvinegar]

One last note: this comment was intentionally made to be 4 lines long because Sentry records 5 frames of before/after context by default. Doing so results in the first line being try {, which looks nice.