Support force `node:sqlite` instead of `bun:sqlite` when enabling native DB connector in Bun

Environment

Version

v3.12.0

Reproduction

https://codesandbox.io/p/devbox/tender-pascal-dyzh65

Description

I'm using Bun locally, and deploy to Cloudflare Workers. When enabling content.experimental.sqliteConnector = 'native' with bun run build, it automatically uses bun:sqlite even though node:sqlite is also supported in Bun, but Cloudflare can't recognize bun:sqlite, so it fails:

[nitro 4:59:23 AM] ℹ Building Nuxt Nitro server (preset: cloudflare-module, compatibility date: 2026-04-05)

[nitro 4:59:30 AM]  ERROR  Error: Cannot resolve "bun:sqlite" from "/project/workspace/node_modules/.pnpm/db0@0.3.4/node_modules/db0/dist/connectors/bun-sqlite.mjs" and externals are not allowed!


undefined

2027 |           if (_resolved) {
2028 |             return { id: _resolved, external: false };
2029 |           }
2030 |         }
2031 |         if (!resolved || resolved.external && !id.endsWith(".wasm")) {
2032 |           throw new Error(
                           ^
error: Cannot resolve "bun:sqlite" from "/project/workspace/node_modules/.pnpm/db0@0.3.4/node_modules/db0/dist/connectors/bun-sqlite.mjs" and externals are not allowed!
     plugin: "commonjs--resolver",
       hook: "resolveId",
 watchFiles: [...],
       code: "PLUGIN_ERROR"

      at resolveId (/project/workspace/node_modules/nitropack/dist/rollup/index.mjs:2032:21)

Maybe there the sqliteConnector can be ... | 'native-node' | 'native-bun' to support explicitly avoid the problem.

Note: Add run.bun = true to bunfig.toml to make sure node xxx child-processes are routed to Bun

Additional context

No response

Logs

Start with the linked CodeSandbox reproduction and inspect how content.experimental.sqliteConnector is handled when building with Bun for the cloudflare-module preset. Check bunfig.toml's run.bun setting as noted in the report. Done means a native connector choice using node:sqlite can build for Cloudflare without bun:sqlite resolution errors.