initSqlJs doesn't throw when wasm cannot be fetched
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.7k
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Description
import initSqlJs from 'sql.js';
(async () => {
await initSqlJs();
})();
The promise will never settle, if the file cannot be fetched. The console will output
Uncaught (in promise) TypeError: Failed to fetch
but the promise remains in the "pending" state, so I guess the fetch is running outside the normal promise chain
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
Start at the initSqlJs entry point and reproduce the case where the WASM file cannot be fetched. Trace the fetch error through initialization and ensure the returned promise rejects rather than remaining pending; verify the failure is observable to the caller.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- database, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100