Jonathan Huang

Hi @lforst, thanks for the response. Here's one more [link](https://nextjs.org/docs/advanced-features/ci-build-caching) that Next.js provides (although it's not very detailed). I'm also not very familiar with Vercel build cache, but I think...

Okay I started a discussion [here](https://github.com/vercel/next.js/discussions/40588) in Next.js. I just tried setting the `SENTRY_RELEASE` but had no luck. Just to confirm, I only set the environment variable at build time...

Thanks for the response @lobsterkatie. Can you say more though? I'm not sure if I fully understand. What would my webpack config look like now?

I'm still getting this as well. Here's a Loom of my issue https://www.loom.com/share/0a5060a25e354fc3a886560ced3426eb

Yes, the issue still exists on 6.1.18

Hmm I'm not sure I understand. I'm not using a backend. I'm just following this [tutorial](https://docs.wasmer.io/sdk/wasmer-js/tutorials/run) and the issue happens on the imported init function. What is the init function...

Okay, I looked into this a little more and I don't think that's the root issue. When I run `vite dev`, the server fetches `http://localhost:5173/node_modules/.vite/deps/wasmer_js_bg.wasm` but that file is an...

Okay I found a solution to the issue. Looks like vite's optimizations are causing issues when packages import using `import.meta.url` (see https://github.com/vitejs/vite/issues/8427). Adding the following in my `vite.config.js` fixed the...