feat(nuxt): Automatically detect environment

[maximepvrt]

Before submitting a pull request, please take a look at our
Contributing guidelines and verify:

• If you've added code that should be tested, please add tests.
• Ensure your code lints and the test suite passes (yarn lint) & (yarn test).

closes #15147

[mydea]

If the console logs are removed, should this be ready to be reviewed? :)

[maximepvrt]

Hi @mydea, as mentioned in the issue, I tried setting up an environment to test locally, but my console.log statements aren't showing up, and I’m not sure if this is normal or if I made a mistake when setting up the local module. I opened the MR to get feedback on whether it's expected not to see the console.log outputs and why the environment setup isn't working on my end. Also, I feel like there’s a lack of a contribution guide, which could help with improving the module.

[maximepvrt]

I attempted to import the module locally using:

export default defineNuxtConfig({
  modules: ['../sentry-javascript/packages/nuxt/src']
})

However, my app gets stuck on "ℹ Vite client warmed up" and doesn’t start.

[mydea]

Ah sorry, I did not connect this to the issue. Somebody from the team will look into it, we are quite swamped right now and parts of the team that have the most knowledge on Nuxt are currently unavailable, so it may take a few days, but we'll try to look into it next week latest!

[s1gr1d]

This looks good in general, please add this to the E2E test as well (here). Regarding testing this locally: You can build the package, then build the tarball and then add this tarball like a npm package in your test application's node_modules. Then you can set up Sentry in Nuxt as you would normally do this.

[lforst]

Closing due to inactivity.