@electric-sql/pglite
0.5.17 · 19 Nov 2026Apache-2.044.2M / weekRepositoryHomepagenpmAtom feed
68 stable releases, newest first, by release line. Notes are quoted as the maintainers published them.
- 0.5.x · latest line
0.5.17
19 Nov 2026Upgrade to PostgreSQL 18.7
0.5.16
9 Nov 2026Export
pglite.wasm,initdb.wasmandpglite.dataso they can be imported by package path (e.g.@electric-sql/pglite/pglite.wasm), and document Nitro/Nuxt support.Parse
infinityand-infinityindate,timestampandtimestamptzvalues asInfinityand-Infinityinstead ofInvalid Date, and serialize them back toinfinityand-infinity.Escape embedded double quotes in
identifiertemplate helper so identifiers containing"produce valid SQL
Patch Changes
Export
pglite.wasm,initdb.wasmandpglite.dataso they can be imported by package path (e.g.@electric-sql/pglite/pglite.wasm), and document Nitro/Nuxt support.Parse
infinityand-infinityindate,timestampandtimestamptzvalues asInfinityand-Infinityinstead ofInvalid Date, and serialize them back toinfinityand-infinity.Escape embedded double quotes in
identifiertemplate helper so identifiers containing"produce valid SQLSerialize query descriptions and wait for database initialization so concurrent operations return the correct parameter and result metadata.
Reset the stream callback after execProtocolRawStream so later execProtocolRaw/execProtocolRawSync calls are not routed to it
0.5.15
3 Nov 2026Reject with
TransactionAbortedErrorwhen committing an aborted transaction rolls it back instead of silently resolving.Reduce initdb memory usage by passing a smaller WebAssembly.Memory object during initialization'
Patch Changes
Reject with
TransactionAbortedErrorwhen committing an aborted transaction rolls it back instead of silently resolving.Reduce initdb memory usage by passing a smaller WebAssembly.Memory object during initialization'
0.5.14
31 Oct 2026Only build the
pglite.wasm,initdb.wasmandpglite.dataURLs when PGlite has to load them. PassingpgliteWasmModule,initdbWasmModuleandfsBundlenow works in bundles whereimport.meta.urlis undefined, such as an esbuild IIFE build.Use PROXYFS instead of dumping the data dir from the scratch PGlite used for initdb when the data dir is in memory.
Do not copy parsers on each query
0.5.13
28 Oct 2026close()now waits for queries, execs and transactions that were issued before it, so they complete instead of failing withCannot read properties of undefinedafter teardown.Added support for node-postgres through createPgConfig()
Added MemfsFrontendFS which allows other filesystems be implemented on top of a MEMFS. Example: added Memfs2OpfsFS which is backed by an OPFS fs.
Patch Changes
close()now waits for queries, execs and transactions that were issued before it, so they complete instead of failing withCannot read properties of undefinedafter teardown.Added support for node-postgres through createPgConfig()
Added MemfsFrontendFS which allows other filesystems be implemented on top of a MEMFS. Example: added Memfs2OpfsFS which is backed by an OPFS fs.
0.5.12
26 Oct 2026Fix custom filesystems not receiving times set with
FS.utime. Emscripten'sFS.utimecallssetattrwithatimeandmtime, but theBaseFilesystembridge only handled the oldertimestampfield, soutimeswas never called on OPFS AHP or any otherBaseFilesystem. Files restored from a tarball kept the time they were written instead of the time stored in the tarball.Run initdb with
TZ=UTC, like the backend, so a new database getstimezone = 'UTC'inpostgresql.conf. Before, initdb wrote the host's zone as a fixed offset without daylight saving (e.g.Etc/GMT+5for America/New_York), sotimestamptzinput without an offset was stored at a different instant on each non-UTC machine.Start under the Node.js permission model (
node --permission). Emscripten's NODEFS read the fs open flags withprocess.binding('constants'), which Node always denies in that mode, sonew PGlite()threwERR_ACCESS_DENIEDeven formemory://. The bundled build now reads them fromrequire('fs').constants, which holds the same values.
Patch Changes
Fix custom filesystems not receiving times set with
FS.utime. Emscripten'sFS.utimecallssetattrwithatimeandmtime, but theBaseFilesystembridge only handled the oldertimestampfield, soutimeswas never called on OPFS AHP or any otherBaseFilesystem. Files restored from a tarball kept the time they were written instead of the time stored in the tarball.Run initdb with
TZ=UTC, like the backend, so a new database getstimezone = 'UTC'inpostgresql.conf. Before, initdb wrote the host's zone as a fixed offset without daylight saving (e.g.Etc/GMT+5for America/New_York), sotimestamptzinput without an offset was stored at a different instant on each non-UTC machine.Start under the Node.js permission model (
node --permission). Emscripten's NODEFS read the fs open flags withprocess.binding('constants'), which Node always denies in that mode, sonew PGlite()threwERR_ACCESS_DENIEDeven formemory://. The bundled build now reads them fromrequire('fs').constants, which holds the same values.Fix files restored from a tarball getting a January 1970 modification time.
loadTarpassed the tar header's time to Emscripten'sFS.utimein seconds, butFS.utimetakes milliseconds. This affected every new database (initdb's data dir is restored from a tarball) and everyloadDataDir. With the Node filesystem the files on disk got those dates too.
0.5.11
21 Oct 2026Bug fix: check ready before close
Update submodule
Fix premature ReadyForQuery responses after extended-query errors, preventing PostgreSQL clients from desynchronizing before Sync.
0.5.10
14 Oct 2026Bug fix: wait for running queries to finish before doing a data dir dump
Wait for queries to finish before closing PGlite instance. See #1128
Fix a windowed
live.query(one givenoffsetandlimit) leaking itslive_query_<id>_get_total_countprepared statement onunsubscribe. Onlylive_query_<id>_getwas deallocated, so the count statement survived every teardown while its backing view was dropped, accumulating dangling prepared statements for the lifetime of the database.
0.5.9
12 Oct 2026Upgrade to PostgreSQL 18.6
Export additional core symbols from the main WASM module required by the plpgsql_check extension
0.5.8
26 Aug 2026Do not set process.exitCode at all
0.5.7
23 Aug 2026Reading the note…
0.5.6
22 Aug 2026Reading the note…
0.5.5
13 Aug 2026Reading the note…
0.5.4
2 Jul 2026Reading the note…
0.5.3
16 Jun 2026Reading the note…
0.5.2
11 Jun 2026Reading the note…
0.5.1
2 Jun 2026Reading the note…
0.5.0
2 Jun 2026Reading the note…
- 0.4.x
0.4.6
25 May 2026Reading the note…
0.4.5
27 Apr 2026Reading the note…
0.4.4
9 Apr 2026Reading the note…
0.4.3
2 Apr 2026Reading the note…
0.4.2
25 Mar 2026Reading the note…
0.4.1
19 Mar 2026Reading the note…
0.4.0
17 Mar 2026Reading the note…
- 0.3.x
0.3.16
10 Mar 2026Reading the note…
0.3.15
15 Jan 2026Reading the note…
0.3.14
6 Nov 2025Reading the note…
0.3.13
5 Nov 2025Reading the note…
0.3.12
3 Nov 2025Reading the note…
0.3.11
14 Oct 2025Reading the note…
0.3.10
24 Sep 2025Reading the note…
0.3.9
22 Sep 2025Reading the note…
0.3.8
8 Sep 2025Reading the note…
0.3.7
4 Aug 2025Reading the note…
0.3.6
28 Jul 2025Reading the note…
0.3.5
15 Jul 2025Reading the note…
0.3.4
26 Jun 2025Reading the note…
0.3.3
4 Jun 2025Reading the note…
0.3.2
21 May 2025Reading the note…
0.3.1
12 May 2025Reading the note…
0.3.0
24 Apr 2025Reading the note…
- 0.2.x
0.2.17
12 Feb 2025Reading the note…
0.2.16
21 Jan 2025Reading the note…
0.2.15
9 Dec 2024Reading the note…
0.2.14
26 Nov 2024Reading the note…
0.2.13
12 Nov 2024Reading the note…
0.2.12
11 Oct 2024Reading the note…
0.2.11
7 Oct 2024Reading the note…
0.2.10
2 Oct 2024Reading the note…
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.