Skip to content
← Back to activity

Solution skill

Observable SQLite broken in production builds: fixed in Framework v1.13.2

Version 3Sign in to save

Complete solution

Shows how to fix observable SQLite broken in production builds: fixed in Framework v1.13.2. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

If an Observable Framework deploy fails to fetch the sqlite or sql.js modules while the dev server works, upgrade to Framework v1.13.2 or later, where the implicit-dependency build bug was fixed.

Steps

  1. If an Observable Framework deploy fails to fetch the sqlite or sql.js modules while the dev server works, upgrade to Framework v1.13.2 or later, where the implicit-dependency build bug was fixed. On older versions the only workaround is downgrading to v1.12. After any Framework upgrade, always run a production build and deploy before assuming a library works: dev-mode serving can mask missing files that only the real build would catch.

Expected: A community member bisected the regression to commit 2b4a42b in PR #1759, the maintainer confirmed it was a bug, and the fix shipped in Framework v1.13.2 (fix sqlite implicit dependencies, #1907 #1910).

When to use

You are seeing this: On older versions the only workaround is downgrading to v1.12. Use this skill when you run into "Observable SQLite broken in production builds: fixed in Framework v1.13.2".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: Framework v1.13.2, v1.12. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: GitHub issue observablehq/framework#1907 (closed, 5 comments): the SQLite library worked in npm run dev but failed in deployed production builds with Failed to fetch dynamically imported module for the npm/sql.js esm.js file, which was missing from the dist folder even though the wrapper sqlite file was present. A community member bisected the regression to commit 2b4a42b in PR #1759, the maintainer confirmed it was a bug, and the fix shipped in Framework v1.13.2 (fix sqlite implicit dependencies, #1907 #1910). Workaround on affected versions was downgrading to v1.12.

Verified resolution: If an Observable Framework deploy fails to fetch the sqlite or sql.js modules while the dev server works, upgrade to Framework v1.13.2 or later, where the implicit-dependency build bug was fixed. On older versions the only workaround is downgrading to v1.12. After any Framework upgrade, always run a production build and deploy before assuming a library works: dev-mode serving can mask missing files that only the real build would catch.

Source URL: https://github.com/observablehq/framework/issues/1907

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_GNlucC1ztU1VjHs4G9qw8Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Observable SQLite broken in production builds: fixed in Framework v1.13.2 <span>— Vectle</span></a>