fix(nextjs): Add environment automatically #3495
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
HazAT
approved these changes
May 4, 2021
Contributor
size-limit report
|
iker-barriocanal
added a commit
to getsentry/sentry-docs
that referenced
this pull request
May 5, 2021
This PR adds the corresponding docs for getsentry/sentry-javascript#3495, where the `process.env.NODE_ENV` is added as the `environment` by default.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Specifying no environment leads events to be marked as production environments. This PR adds the
environmentfromprocess.env.NODE_ENVby default, without keeping users from setting their own environment.