Module "buffer" has been externalized for browser compatibility

[tiagoapp]

I believe this issue is related to Vite itself... but have been trying several options including the settings available on the docs here and can't get Metaplex JS SDK to work due this error.

Module "buffer" has been externalized for browser compatibility

Any ideas how to solve this?

[silvestrevivo]

@tiagoapp is this only happening trying to work with the new Metaplex JS SDK ? you are not the first reporting issues with that. I can get it working on dev, but not in production.

Why do you think this an issue just only related with Vite?

[tiagoapp]

I've only experienced actual issues with new Metaplex JS SDK. But if you spin off a new SvelteKit app with the instructions you've here (or the instructions on Metaplex / Vite examples) this message shows up right away.

I've tried Nuxt.js / Vue which also relies on Vite and also have same Buffer / Global, etc. issues. In that case it does even kills the app altogether.

So far I can only get this running smoothly with Next.js / React - which don't uses Vite.

[silvestrevivo]

@tiagoapp thanks for the investigation. Definitely this is a conflict between those two things. Now it's time to figure out which part is creating/causing the bug.