Support environment attribute

[dcramer]

Maybe we can also default to NODE_ENV when possible.

This is fairly high priority.

[dcramer]

temporary workaround for some legacy users getsentry/sentry#3769

[mattrobenolt]

How would a NODE_ENV be applicable here? Since your artifacts are compiled. Unless this is a convention I'm not aware of where this will get compiled in during build?

[dcramer]

@mattrobenolt Yeah I guess maybe there's no way to use that. I was thinking that possibly during compile time it gets bound and we can read it somehow from common.js type stuff.

[urbany]

Is there a way to currently send the environment through client side raven-js?

[dcramer]

@urbany I dont believe its yet supported top level, but you could use dataCallback and add it there.

[urbany]

@dcramer thanks for the quick reply, can you give me an example on how to do that? What I want is to send the current app environment on each error report.
Thanks in advance : )

[dcramer]

@urbaniak

Raven.config({
    dataCallback: function(data) { data.environment = 'production'; }
})

[urbany]

@dcramer awesome, thank you very much!