Use Raven.noConflict() when exporting as AMD module

[ThisIsMissEm]

This cleans up the global namespace a bit.

[mattrobenolt]

What's the issue this is trying to solve? I based my implementation on jQuery. Not that it's the best example, but I was just following suit. :)

See: https://github.com/jquery/jquery/blob/master/src/exports.js

[mattrobenolt]

I also have plans for plugins, and not having a global Raven will mess them up. Not sure how to solve this, so I'm hesitant without thinking it fully through.

[mattrobenolt]

Eh, I'll deal with it later. I have some ideas.

[ThisIsMissEm]

I think it'd still be possible to have an plugin architecture. You just need to make sure that they can register with Raven... We actually have stuff that we do with raven which is pretty much a plugin, or maybe more a wrapper to give us certain functionality.

[ThisIsMissEm]

The main thing that this addresses is the fact that an AMD module shouldn't change the environment when it is loaded.