Automatically set environment to `development` in Nuxt dev mode

[maximepvrt]

Is there an existing issue for this?

• I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
• I have reviewed the documentation https://docs.sentry.io/
• I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nuxt

SDK Version

8.51.0

Framework Version

Nuxt 3.14.1592

Link to Sentry event

https://benevolt.sentry.io/issues/6239844009/?project=4508678079905792&query=is%3Aunresolved%20level%3Aerror&referrer=issue-stream&statsPeriod=14d&stream_index=8

Reproduction Example/SDK Setup

No response

Steps to Reproduce

1. Create a Nuxt.js application.
2. Install and configure Sentry by following the official documentation.
3. Launch the application in development mode with pnpm dev.
4. Generate a JavaScript error in the application.
5. Check the environment associated with the error in Sentry.

Expected Result

The environment should be automatically detected as "development".

Suggestions

Disable by default in development mode: An option to disable Sentry by default in development mode could be added. This would prevent sending development errors to Sentry, which can be annoying.

Actual Result

The environment reported in Sentry is "production".

[andreiborza]

Hi @maximepvrt, thanks for filing this.

As we don't currently recommend users to use the development mode when using our SDK it's probably of lower priority on our plate. Disabling Sentry by default in development mode is probably something we'll leave up to users, but we could for example set the environment option in the SDK's inits (for both client and server) to development by looking at import.meta.env.DEV.

Would you be up for contributing such a change?

[maximepvrt]

Hi @andreiborza, I've tried implementing the automatic environment detection with process.env.NODE_ENV, but I noticed that it's not working because my console logs aren't showing up. I tried testing it locally by importing the Sentry module as follows:

import MyModule from '../sentry-javascript/packages/nuxt/src/module'

export default defineNuxtConfig({
  modules: [MyModule],
})

I've also opened a PR for Nuxt to use import.meta.envName for environment handling in the future: nuxt/nuxt#30765.

[andreiborza]

@maximepvrt thanks for directly improving that in nuxt! Once that lands we can make use of it in the client/server inits but we'd have to have some fallback on import.meta.env.DEV probably.

Did you try with import.meta.env.DEV?