electron-webpack build

Open

#404 opened on Jun 15, 2020 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 4/5
Estimated time: 3-5 days
Newbie friendliness: 25/100

Issue type: Bug
Clarity: Needs clarification
Activity status: Stale
Tech stack: electron, javascript, sqlite, wasm
Domain: build-system, databases, desktop

Research direction

Start by reproducing the sample repository linked in the issue and inspect sql-wasm.js alongside the sql-wasm.wasm asset. Trace why the generated application requests the file from node_modules and why the initial wasm load produces a syntax error; done means the Electron build loads sql.js without either reported error.

Written by the indexing model from the issue text.

Description

question

Hi there,

I am using electron-webpack to pack sql.js into an electron app, but getting the below errors.
The first error appears to have an issue with the sql-wasm.wasm file.

Uncaught SyntaxError: Invalid or unexpected token

The second error is because electron-webpack seems to want to still load the sql-wasm.wasm file from node_modules despite being copied over to js/sql-wasm.wasm output already.

/home/stuart/dev/ele…ist/sql-wasm.js:167 GET http://localhost:9080/home/stuart/dev/electron-svelte-typeorm-typescript/node_modules/sql.js/dist/sql-wasm.wasm 404 (Not Found)

/home/stuart/dev/ele…ist/sql-wasm.js:167 wasm streaming compile failed: TypeError: Failed to execute 'compile' on 'WebAssembly': HTTP status code is not ok

/home/stuart/dev/ele…ist/sql-wasm.js:167 falling back to ArrayBuffer instantiation

GET http://localhost:9080/home/stuart/dev/electron-svelte-typeorm-typescript/node_modules/sql.js/dist/sql-wasm.wasm 404 (Not Found)

Any thoughts would be appreciated. The sample repo is at https://github.com/eightfivelabs/electron-svelte-typeorm-typescript

Dominant language: JavaScript
Stars: 13.7k
Forks: 1.1k
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing 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.

Similar issues

Ajv defaults: non-standard "format": "json" in third-party schemas (e.g. Notion) warns twice per property — register it like #2601 Open

Difficulty 2/5 1-3 hours Newbie friendliness 70/100

modelcontextprotocol/typescript-sdk#2854 · Opened Sep 24, 2026
[Bug]: ctx_search rejects singular 'query' param despite schema declaring it valid Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

mksglu/context-mode#1200 · Opened Sep 24, 2026
Duplicated 'Connect to Database Using C#' link in Postgres Tutorial Page Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

neondatabase/website#5944 · Opened Sep 24, 2026
bbb-conf --set-port-range writes port values as YAML strings, so mediasoup ignores the configured range Open

module: core

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

bigbluebutton/bigbluebutton#25849 · Opened Sep 24, 2026
[chore]: test(search): Migrate ResultItemTitle unit tests to TypeScript Open

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

jaegertracing/jaeger-ui#4506 · Opened Sep 24, 2026

More JavaScript issues