# SQL cells not working (since switching to imports from esm.sh?) **URL:** \ **Category:** Help\ **Created:** [November 9, 2026, 8:45pm UTC](https://talk.observablehq.com/t/sql-cells-not-working-since-switching-to-imports-from-esm-sh/10967 "2026-11-09T20:45:14Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![Jakob](https://avatars.discourse-cdn.com/v4/letter/j/71c47a/32.png) [@Jakob](https://talk.observablehq.com/u/Jakob)\ **Post date:** [November 9, 2026, 8:45pm UTC](https://talk.observablehq.com/t/sql-cells-not-working-since-switching-to-imports-from-esm-sh/10967/1 "2026-11-09T20:45:15Z")
Since Sunday, Nov 9, SQL cells no longer run for me. I can reproduce it in the [Notebooks system guide](https://observablehq.com/@observablehq/notebooks-system-guide): the SQL cell only shows the loading spinner. The browser console shows: > async\_bindings.ts:307 error in duckdb worker: Uncaught NetworkError: Failed to execute ‘importScripts’ on ‘WorkerGlobalScope’: The script at ‘[https://esm.sh/@duckdb/duckdb-wasm@1.32.0/dist/duckdb-browser-eh.worker.js](https://esm.sh/@duckdb/duckdb-wasm@1.32.0/dist/duckdb-browser-eh.worker.js)’ failed to load. Is anyone else experiencing this issue? Is this perhaps related to the switch to imports from esm.sh? Thank you! 🙂 PS: I do really enjoy the new Observable – Thank you so much for all your effort! ---
**Author:** ![mbostock](https://yyz2.discourse-cdn.com/flex030/user_avatar/talk.observablehq.com/mbostock/32/9_2.png) [@mbostock](https://talk.observablehq.com/u/mbostock)\ **Post date:** [November 9, 2026, 8:50pm UTC](https://talk.observablehq.com/t/sql-cells-not-working-since-switching-to-imports-from-esm-sh/10967/2 "2026-11-09T20:50:44Z")
Oops, confirmed. The DuckDB worker script needs to bypass esm.sh’s bundling using `?raw`. Thanks for the report! I’ll get a fix out shortly. Edit: fix deployed.