astro build --remote fails using Cloudflare adapter + Astro DB remote: Invalid URL string.

[BalsamLawson]

Astro Info

Astro                    v6.1.1
Vite                     v7.3.1
Node                     v22.18.0
System                   Windows (x64)
Package Manager          npm
Output                   static
Adapter                  @astrojs/cloudflare (v13.1.4)
Integrations             astro:db
                         @astrojs/db/file-url

If this issue only occurs in one browser, which browser is a problem?

No response

Describe the Bug

I had an Astro site with AstroDB working fine in dev but could not get it to deploy to Cloudflare pages using a remote db hosted by Turso. No matter what I tried, the build always failed with:
Invalid URL string.
Location:

  ..../node_modules/.vite/deps_ssr/chunk-4647JXVN.js?v=6cff316a:63:14
    at Object.runInlinedModule (workers/runner-worker/index.js:218:4)
    at CustomModuleRunner.cachedRequest (workers/runner-worker/vite/module-runner:1111:73)
    at Object.runInlinedModule (workers/runner-worker/index.js:218:4)
    at CustomModuleRunner.cachedRequest (workers/runner-worker/vite/module-runner:1111:73)

All the usual suspects of mis-specified environment variables, bad url or access tokens did nothing to solve the problem. npx astro db push works so the ASTRO_DB_REMOTE_URL and ASTRO_DB_APP_TOKEN .env parameters appear to be correct. After hours of troubleshooting and countless permutations, compatibility flags, wrangler.toml tweaks, etc. I could never get past this. So I started on a fresh Windows machine, built a minimal example, and I'm running into the exact same issue when building locally. I think there's something deeper going on specifically with the interaction between Astrodb and the Cloudflare adapter.

Since StackBlitz does not support @astrojs/cloudflare here's a summary of the minimal steps.

On Windows, an otherwise minimal Astro v6 project using @astrojs/db (remote/libSQL) and the Cloudflare adapter fails during astro build --remote with Invalid URL string.. This appears to be a Windows path vs file:// URL serialization bug: during SSR/module-runner setup the manifest is deserialized and code attempts new URL(serializedManifest.rootDir) (and similar), but at least one of those fields is not a valid URL.

Environment

• OS: Windows 10 (10.0.19045)
• Shell: PowerShell
• Node: v22.18.0
• npm: 11.5.2
• astro: 6.1.1
• @astrojs/db: 0.20.1
• @astrojs/cloudflare: 13.1.4
• wrangler: 4.77.0

Minimal repro steps

1. Create a new project:

npm create astro@latest . -- --template basics --install --git false

Add Astro DB and define a single table:
npx astro@latest add db --yes

db/config.ts:

import { defineDb, defineTable, column } from 'astro:db';
export default defineDb({
  tables: {
    Items: defineTable({
      columns: {
        id: column.number({ primaryKey: true }),
        name: column.text(),
      },
    }),
  },
});

Add Cloudflare adapter:
npx astro@latest add cloudflare --yes

astro.config.mjs:

import { defineConfig } from 'astro/config';
import db from '@astrojs/db';
import cloudflare from '@astrojs/cloudflare';
export default defineConfig({
  integrations: [db()],
  adapter: cloudflare(),
});

Configure DB remote env vars (example; token redacted):

.env:

ASTRO_DB_REMOTE_URL=libsql://<your-db>.turso.io
ASTRO_DB_APP_TOKEN=<redacted>

Build with remote mode:
npm run build --remote

Build fails:

[ERROR] [astro:db] An unhandled error occurred while running the "astro:build:setup" hook
Invalid URL string.
  Location:
    C:/Users/.../node_modules/.vite/deps_ssr/chunk-4647JXVN.js?...:63:14
  Stack trace:
    at deserializeManifest (...)
    at Object.runInlinedModule (workers/runner-worker/index.js:218:4)

Additional details / suspected root cause
The thrown error originates from code equivalent to:

rootDir: new URL(serializedManifest.rootDir),
srcDir: new URL(serializedManifest.srcDir),
publicDir: new URL(serializedManifest.publicDir),
outDir: new URL(serializedManifest.outDir),
cacheDir: new URL(serializedManifest.cacheDir),

If any of these values are plain Windows paths (e.g. C:... or C:/...) rather than valid file:// URLs, new URL(...) will throw Invalid URL string..

This only reproduces once:

Cloudflare adapter is enabled (build mode becomes server), and
Astro DB remote build is enabled (--remote)

This appears to be the exact same problem I was experiencing in Cloudfare deployments. Happy to provide any additional information. This is a show-stopper at the moment!

What's the expected result?

astro build --remote should complete successfully (or fail with a clear DB connection/auth error if credentials are wrong), not with Invalid URL string

Link to Minimal Reproducible Example

https://stackblitz.com/edit/github-ak5ik59o?file=astro.config.mjs

Participation

• I am willing to submit a pull request for this issue.

[astrobot-houston]

I was able to reproduce this issue. The root cause is in the @astrojs/db integration's astro:build:setup hook, which creates a temporary Vite dev server (getTempViteServer()) using the full build Vite config — including @cloudflare/vite-plugin. The Cloudflare plugin creates a workerd-based SSR environment that eagerly imports the manifest module, which at that point still contains a build-time placeholder string instead of valid URLs. This causes deserializeManifest() to call new URL() on an invalid string, throwing Invalid URL string.. Notably, this is not a Windows-specific issue — it reproduces on Linux as well.

I was able to fix this issue. The fix filters out @cloudflare/vite-plugin and its sub-plugins from the temporary Vite server, since it only needs a standard Node.js SSR environment for executing seed files. View Suggested Fix

P5: urgent. This is a build-breaking bug that affects all users combining @astrojs/db (remote mode) with the @astrojs/cloudflare adapter. There is no workaround — astro build --remote is completely non-functional in this configuration, blocking any Cloudflare deployment that uses Astro DB with a remote database.

Full Triage Report

Original Issue

Title: astro build --remote fails using Cloudflare adapter + Astro DB remote: Invalid URL string.

Reporter: BalsamLawson

Description: When using @astrojs/db with the Cloudflare adapter (@astrojs/cloudflare), running astro build --remote fails with Invalid URL string. during the astro:build:setup hook. The error originates from deserializeManifest() when it tries to construct new URL() from manifest directory fields (rootDir, srcDir, etc.) that contain invalid placeholder strings instead of valid file:// URLs.

Environment:

• Astro: v6.1.1
• @astrojs/db: 0.20.1
• @astrojs/cloudflare: 13.1.4
• Node: v22.18.0
• OS: Windows 10 (but also reproducible on Linux)

Reproduction

Status: REPRODUCED

Reproduced on Linux (CI sandbox) using a minimal Astro project with @astrojs/db and @astrojs/cloudflare.

Steps:

1. Created minimal project from examples/minimal template
2. Added @astrojs/db and @astrojs/cloudflare to dependencies
3. Created db/config.ts with a single table definition
4. Created .env with ASTRO_DB_REMOTE_URL and ASTRO_DB_APP_TOKEN
5. Ran astro build --remote

Error output:

[ERROR] [astro:db] An unhandled error occurred while running the "astro:build:setup" hook
Invalid URL string.
  Stack trace:
    at deserializeManifest (/home/runner/work/astro/astro/packages/astro/dist/core/app/manifest.js:37:14)
    at Object.runInlinedModule (workers/runner-worker.js:1314:4)
    at CustomModuleRunner.cachedRequest (workers/runner-worker.js:1084:73)

Diagnosis

Root Cause: The @astrojs/db integration's astro:build:setup hook creates a temporary Vite dev server (getTempViteServer() in packages/db/src/core/integration/index.ts:247) to execute seed files. This temp server inherits the full build Vite config, including @cloudflare/vite-plugin. The Cloudflare plugin creates a workerd-based SSR environment that eagerly imports the manifest virtual module. During the build, this module contains a placeholder string (not a valid URL) that will be replaced later. The workerd environment imports the placeholder before replacement, causing deserializeManifest() to crash when calling new URL() on the invalid string.

Confidence: HIGH

Verification

Verdict: BUG — No code comments, design rationale, or prior discussion indicates this interaction was intended. The temp server only needs a Node.js SSR environment for seed files.

Confidence: HIGH

Fix

The fix filters out all @cloudflare/vite-plugin sub-plugins (all named with prefix vite-plugin-cloudflare) from the temporary Vite server config. The change is in packages/db/src/core/integration/index.ts, in the getTempViteServer() function.

Verification:

• Before fix: astro build --remote crashes with Invalid URL string.
• After fix: Build proceeds past the astro:build:setup hook successfully

This report was made by an LLM. Mistakes happen, check important info.

[BalsamLawson]

If anybody has Astro working with Cloudflare / Turso would you be so kind as to post the version(s) you are using? I've only ever had a 100% static site in production so I don't have the skillset to patch or work around this myself without moving hosting providers which I'd prefer not to do. Figured it might be easier to roll back to known working prior version(s). Thank you!

[matthewp]

Astrobot, please try again with the latest code.