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.

Context: 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.

## Matched source
Source: Published skill
Original query: "Observable SQLite broken in production builds: fixed in Framework v1.13.2"
Key terms: broken, builds, fixed, framework, observable, production, sqlite
