Identifier '$haml' has already been declared

[rnenjoy]

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.25.0

Framework Version

3.12.4

Link to Sentry event

No response

Reproduction Example/SDK Setup

https://github.com/rnenjoy/sentry-nuxt-bug

Steps to Reproduce

pnpm run dev

Expected Result

Instrument as usual

Actual Result

Cannot start nuxt: Identifier '$haml' has already been declared 11:31:58 AM

at compileSourceTextModule (node:internal/modules/esm/utils:337:16)
at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:163:18)
at callTranslator (node:internal/modules/esm/loader:430:14)
at ModuleLoader.moduleProvider (node:internal/modules/esm/loader:436:30)

[s1gr1d]

Hello, thanks for reaching out. I see that you added the node options to almost all scripts. You only need to add them to the scripts that are running your build output:

"preview": "NODE_OPTIONS='--import ./public/instrument.server.mjs' nuxt preview",
"start": "NITRO_PORT=4000 NITRO_HOST=0.0.0.0 node  --import .output/public/instrument.server.mjs .output/server/index.mjs"

In general, we optimize for the production build of applications. And thanks for filing the issue, I will make this more clear in the docs :)

[rnenjoy]

Makes sense! Sorry for that @s1gr1d !

[s1gr1d]

You're welcome! However, I fixed this and you should be able to add the --import flag in dev mode with v8.26.0

[florian-lefebvre]

Hi! I know this is a closed issue but I'm facing this issue in an Astro project while trying to upgrade to >=8.0. I can't manage to make a reproduction atm so I'm trying to find clues about what could be causing this, and be able to report it properly. Do you know why this error occurs at all?

[s1gr1d]

Please be so kind and open a new issue with some more information so we can better keep track of this, thanks :)
Feel free to reference this issue.