Destructive error when building with Vite

[FeiFanLiang]

When building, the error this?.debug is not a function will be prompted.
I solved the problem by manually deleting these two lines in the code, but the built product did not run properly.

I used Typescript's alias,This resulted in the project not being able to find the page file for the response.
This problem occurs when I turn on stringArray and builds normally when turned off, but I would really like to use this option

I uploaded a minimally reproducible code to the warehouse, and I only need to run pnpm build pnpm preview to reproduce it.
https://github.com/FeiFanLiang/rollup-obfuscator-debugger

[GabrielMahan]

experiencing this as well.

[GabrielMahan]

Not totally sure how the debugging stuff is supposed to work, but I made a quick PR to address: #149.

[ghostdevv]

@GabrielMahan @FeiFanLiang could you confirm that this is now fixed in v4.1.1?

[thierrymichel]

No, I still have a similar issue.
Removing the 2 this.debug lines does not change anything.

I do not have time (right now) to create a minimal reproducible example but what I observed :

• Happens with stringArray: true
• Generates errors on build like:
  • src/modules/ui/App.vue (1:964): Error when using sourcemap for reporting an error: Can't resolve original location of error.
  • not always the same files (kind of randomness)!
• Crash the application with resolution error:
  • TypeError: Failed to resolve module specifier '@/modules/ui/views/Idle.vue' (which is imported in the App.vue…)
  • not always in the same way
  • probably related to the random behavior (see upper)

I will try to make it reproducible somewhere later.

[thierrymichel]

FYI, similar behaviour with rollup-plugin-obfuscator

[z0ffy]

Try it with https://www.npmjs.com/package/vite-plugin-bundle-obfuscator