-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Identifier '$haml' has already been declared #13304
Comments
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:
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 :) |
Makes sense! Sorry for that @s1gr1d ! |
You're welcome! However, I fixed this and you should be able to add the |
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? |
Please be so kind and open a new issue with some more information so we can better keep track of this, thanks :) |
Is there an existing issue for this?
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)
The text was updated successfully, but these errors were encountered: