`pg` bundling isuses with nitro v3 and cloudflare

[medz]

Describe the feature

While using Nitro, the current bundler has encountered many strange issues, such as:

• WASM cannot extend beyond the project scope.

• The runtime requires WASM, but it doesn't handle platform-compliant formats well.

• External non-standard ESM dependencies (e.g., Prisma ORM, many of its dependencies are CJS, or pg packages, whose ESM support requires writing an ESM file that depends on internal CJS).

• Non-standard Node module dependencies, such as require("events").

These problems often occur with Cloudflare workers, and updating the current bundling configuration makes it difficult to handle various situations (usually occurring in other dependent packages).

Through testing, wrangler's built-in bundling handles all platform-compliant situations. For example, Hono is clever in that it doesn't handle bundling itself, so using Hono in the same situation works without problems.

For example, a recent problem I encountered involved needing to depend on Prisma ORM and then using the pg driver. Bundling was flawless, but deployment to Cloudflare failed.

---

Q: So, what is pure packaging mode support?

Simply put, Nitro doesn't handle any packaging; it simply writes the code from a virtual directory to a specific folder and provides an entry file. Alternatively, Nitro provides a virtual entry point (which the user imports and then re-exports).

This way, all code dependencies are located in the original TS/JS files and the pkg folder under node_modules.

Major Benefits

Cloudflare deployment will no longer be hindered; for example, features like cloudflare.exports.ts can be omitted.

Implementation Difficulty

Not yet investigated, but based on previous understanding of Nitro's internal packaging:

1. You still need to run nitro build.

2. Set builder in nitro.config.ts to false to support pure packaging mode.

Additional information

• Would you be willing to help implement this feature?

[pi0]

Thanks for the writeup.

Nitro uses rollup, rolldown or vite for bundling production code and there might be bundling issues, so i appreciate any reproduction of the issues you are mentioning above.

(also please mention if you are using nitro v3 with rolldown or older nitropack v2 with rollup)

There is a new standard preset that writes just a fetch export handler woth no platform handling but i don’t suppose in larger projects, wrangler (esbuild) would handle dependencies better than rolldown. (also note that node polyfills in wrangler is based on unjs/unenv that nitro uses)

[medz]

@pi0 Yes, Wrangler (esbuild) isn't as powerful as Vite/rolldown. However, for NPM packages with Cloudflare-compatible configurations, Wrangler is faster.

Indeed, Wrangler has made many rule optimizations for Cloudflare compatibility. I've only looked at one fetch preset, but I haven't verified it yet; I need to try it out. Because Nitro's greatest appeal is its filesystem routing.

I'm using Nitro v3 + Rolldown

[medz]

This results in issues where, if pg is used and Nitro v3 + Rolldown is used for packaging, the build process is successful, but deployment on Cloudflare fails.

Verified:

1. Deployment with pure TS dependencies + Wrangler (using esbuild for packaging) works without problems.
2. Deployment with Nitro v3 + Rolldown + Wrangler compiles successfully, but deployment fails.

[medz]

I'll write a minimal, reproducible repository later ❤️

[pi0]

This results in issues where, if pg is used and Nitro v3 + Rolldown is used for packaging,

Thanks, lets investigate this 👍🏼