uncaught referenceerror: cannot access 'L' before initialization

[YudhistiraA]

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/vue

SDK Version

7.80

Framework Version

No response

Link to Sentry event

No response

SDK Setup

    if(import.meta.env.VITE_SENTRY_ORG_DSN_XXX) {
      Sentry.init({
                    app,
                    dsn                     : import.meta.env.VITE_SENTRY_ORG_DSN,
                    environment             : import.meta.env.VITE_APP_ENV,
                    integrations            : [
                      new Sentry.Replay(),
                    ],
                    replaysSessionSampleRate: import.meta.env.VITE_SENTRY_ORG_REPLAY_SESSION_SAMPLE_RATE,
                    replaysOnErrorSampleRate: import.meta.env.VITE_SENTRY_ORG_REPLAY_ON_ERRORSAMPLE_RATE,
                  });
    }
  },

Steps to Reproduce

runs fine when run but gets the error during build

Expected Result

will be fine and works well

Actual Result

get
uncaught referenceerror: cannot access 'L' before initialization

[mydea]

Hello,

could you maybe provide a bit more details on your error? A stacktrace would be helpful (e.g. what you see when you click on @sentry-internal-dxxxxx in the console), or if you have it, a link to a sentry issue captured for this (if this was captured by Sentry).

[inikoo]

hello, this it what is shown when click on @sentry-internal-dxxxxx

it is never captured by sentry

[inikoo]

It was working in previous versions of sentry (2 weeks ago) it broke in one the last release , usually update npm packages every couple of weeks

[mydea]

Hmm, weird. Also the SDK version you mentioned 7.80 does not exist yet - the latest is 7.77. What version exactly are you on?

Can you try building without minification (or in dev mode) and see if it happens there as well? It's hard to say where this come from based on the minified stracktrace.

[inikoo]

hello, sorry for send the minify version :P

[inikoo]

I installed the package like this:

npm install --save @sentry/vue

npm -v @sentry/vue
9.6.7

[mydea]

I wonder, how do you build your application? And could you check your lockfile to make sure only a single version of all the SDK packages is installed (e.g. you don't have leftover older versions somewhere - this can sometimes conflict!)

[inikoo]

`"private": true,
"type": "module",
"scripts": {
"build.organisation": "vite build --config vite.organisation.config.js --minify false",
},

i using vite`

[inikoo]

looks like is only version 7.77

[inikoo]

Note that if i use version 7.74.0 or lower it works ok the problem start if install from 7.75

"@sentry/vue": "7.74.0",

has no problem

[AbhiPrasad]

Can you provide a reproduction with a bare-bones vue+vite app? I was unable to reproduce with a test app.

[inikoo]

Ohhhh i found what causing the problem in

vite.config.js

i had this build config:

  build  : {
        rollupOptions: {
          output: {
            manualChunks(id) {
              if (id.includes('node_modules')) {
                return id.toString().
                    split('node_modules/')[1].split(
                    '/')[0].toString();
              }
            },
          },
        },
      },

after removing that all versions works 🥳 , so all ok, but just let you know, sentry is not compatible with that vite build conf,

you can close this issue if you want

[AbhiPrasad]

I think the build config issues might be from the @sentry/ and @sentry-internal prefix on the packages.

Closing - please let us know if there are any other issues. Thanks!

[one-flower]

May I ask if the current new version has fixed this issue?

[Anton-Zelenkov]

Still have this problem. It is observed in Vitе if manual chunking is set:

It can be fixed this way:

[m-Jawa-d]

This solution has worked just remove build object from vite.config.js