carlo-bilby

@zce Interesting. But I don't use `npm-run-all` at all. I only followed: [velite.js.org/guide/with-nextjs#🎊-start-velite-with-next-js-config-🆕](https://velite.js.org/guide/with-nextjs#%F0%9F%8E%8A-start-velite-with-next-js-config-%F0%9F%86%95) (Start Velite with Next.js Config 🆕) I also did 1 or the other for the `build` script:...

I have removed everything related to Velite in the next.config.js. I also have velite.config.ts. I only have this in my package.json: ```jsonc "build": "npx velite && pnpm next build", //...

Hmmm for some reason I can finally deploy when I downgraded the related **esbuild** version from 0.25.3 to 0.25.1. I definitely feel like the culprit here was using the wrong...

Hi @zce. So I managed to find the fix!!! I had to do `pnpm patch`. The reason for the bad import was actually because velite's package.json doesn't contain `"main": "dist/index.js"`...