[Bug]: npm run dev crashes on SQL error

[jcalfee]

Describe the bug

npm run dev crashes on certain SQL error type.

Steps to Reproduce

SELECT ln(0)

Refresh: localhost:3000

Logs

Error: Out of Range Error: cannot take logarithm of zero
    at Et.runQuery (/home/james/dev/ipall/reports/node_modules/@duckdb/duckdb-wasm/dist/duckdb-node-blocking.cjs:70:83828)
    at fr.query (/home/james/dev/ipall/reports/node_modules/@duckdb/duckdb-wasm/dist/duckdb-node-blocking.cjs:70:71372)
    at Module.query (file:///home/james/dev/ipall/reports/node_modules/@evidence-dev/universal-sql/src/client-duckdb/node.js:156:23)
    at Module.query (/home/james/dev/ipall/reports/.evidence/template/src/pages/+layout.js:147:26)
    at Module.profile (/home/james/dev/ipall/reports/node_modules/@evidence-dev/component-utilities/src/profile.js:13:96)
    at queryFunc (/home/james/dev/ipall/reports/.evidence/template/src/pages/èvvin/issuance/draft/+page.md:77:66)
    at __vite_ssr_import_4__.resolveMaybePromise.#error (/home/james/dev/ipall/reports/node_modules/@evidence-dev/sdk/src/usql/query/Query.js:358:10)
    at Module.resolveMaybePromise (/home/james/dev/ipall/reports/node_modules/@evidence-dev/sdk/src/usql/utilities/resolveMaybePromise.js:14:73)
    at #fetchData (/home/james/dev/ipall/reports/node_modules/@evidence-dev/sdk/src/usql/query/Query.js:337:42)
    at Query.fetch (/home/james/dev/ipall/reports/node_modules/@evidence-dev/sdk/src/usql/query/Query.js:378:68)

Node.js v22.7.0

System Info

"dev": "evidence dev --open /",
...
    "@evidence-dev/bigquery": "^2.0.9",
    "@evidence-dev/core-components": "^5.0.2",
    "@evidence-dev/csv": "^1.0.14",
    "@evidence-dev/databricks": "^1.0.8",
    "@evidence-dev/duckdb": "^1.0.13",
    "@evidence-dev/evidence": "^40.0.2",
    "@evidence-dev/motherduck": "^1.0.4",
    "@evidence-dev/mssql": "^1.1.2",
    "@evidence-dev/mysql": "^1.1.4",
    "@evidence-dev/postgres": "^1.0.7",
    "@evidence-dev/snowflake": "^1.2.2",
    "@evidence-dev/sqlite": "^2.0.7",
    "@evidence-dev/trino": "^1.0.9",

Severity

annoyance

Additional Information, or Workarounds

No response