Does not work in node as advertised
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
With given package.json:
{
"type": "module",
"packageManager": "pnpm@7.1.2",
"dependencies": { "sql.js": "1.7.0" }
}
Here's the result of node -e 'require("sql.js")()':
(node:31583) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
node:internal/deps/undici/undici:4813
throw new TypeError("Failed to parse URL from " + input, { cause: err });
^
TypeError: Failed to parse URL from /home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.wasm
at new Request (node:internal/deps/undici/undici:4813:19)
at Agent.fetch2 (node:internal/deps/undici/undici:5505:29)
... 4 lines matching cause stack trace ...
at /home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.js:158:505
at new Promise (<anonymous>)
at initSqlJs (/home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.js:22:24)
at [eval]:1:18 {
[cause]: TypeError [ERR_INVALID_URL]: Invalid URL
at new NodeError (node:internal/errors:377:5)
at URL.onParseError (node:internal/url:563:9)
at new URL (node:internal/url:643:5)
at new Request (node:internal/deps/undici/undici:4811:25)
at Agent.fetch2 (node:internal/deps/undici/undici:5505:29)
at Object.fetch (node:internal/deps/undici/undici:6332:20)
at fetch (node:internal/bootstrap/pre_execution:196:25)
at /home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.js:158:271
at /home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.js:158:492
at /home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.js:158:505 {
input: '/home/[redacted]/node_modules/.pnpm/sql.js@1.7.0/node_modules/sql.js/dist/sql-wasm.wasm',
code: 'ERR_INVALID_URL'
}
}
Node.js v18.3.0
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with the shown package.json and Node.js command, then inspect dist/sql-wasm.js alongside dist/sql-wasm.wasm. Compare the Node loading path with the package's advertised usage; done means the reported require("sql.js")() invocation works under Node.js 18 without the invalid URL error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js, sqlite, wasm
- Domain
- backend, databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100