[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@electric-sql/pglite (source)	0.5.8 → 0.5.14

---

Release Notes

electric-sql/pglite (@​electric-sql/pglite)

v0.5.14

Compare Source

Patch Changes

• 1cf7e86: Only build the pglite.wasm, initdb.wasm and pglite.data URLs when PGlite has to load them. Passing pgliteWasmModule, initdbWasmModule and fsBundle now works in bundles where import.meta.url is undefined, such as an esbuild IIFE build.
• 48dd3fb: Use PROXYFS instead of dumping the data dir from the scratch PGlite used for initdb when the data dir is in memory.
• 268929b: do not copy parsers on each query

v0.5.13

Compare Source

Patch Changes

• c7dc39e: close() now waits for queries, execs and transactions that were issued before it, so they complete instead of failing with Cannot read properties of undefined after teardown.
• 8364675: Added support for node-postgres through createPgConfig()
• a4cfd4d: Added MemfsFrontendFS which allows other filesystems be implemented on top of a MEMFS. Example: added Memfs2OpfsFS which is backed by an OPFS fs.
• 2db5d2d: Upgrade emsdk to 6.0.5

v0.5.12

Compare Source

Patch Changes

• 0641b37: Fix custom filesystems not receiving times set with FS.utime. Emscripten's FS.utime calls setattr with atime and mtime, but the BaseFilesystem bridge only handled the older timestamp field, so utimes was never called on OPFS AHP or any other BaseFilesystem. Files restored from a tarball kept the time they were written instead of the time stored in the tarball.
• e752dbe: Run initdb with TZ=UTC, like the backend, so a new database gets timezone = 'UTC' in postgresql.conf. Before, initdb wrote the host's zone as a fixed offset without daylight saving (e.g. Etc/GMT+5 for America/New_York), so timestamptz input without an offset was stored at a different instant on each non-UTC machine.
• c31130c: Start under the Node.js permission model (node --permission). Emscripten's NODEFS read the fs open flags with process.binding('constants'), which Node always denies in that mode, so new PGlite() threw ERR_ACCESS_DENIED even for memory://. The bundled build now reads them from require('fs').constants, which holds the same values.
• 0641b37: Fix files restored from a tarball getting a January 1970 modification time. loadTar passed the tar header's time to Emscripten's FS.utime in seconds, but FS.utime takes milliseconds. This affected every new database (initdb's data dir is restored from a tarball) and every loadDataDir. With the Node filesystem the files on disk got those dates too.

v0.5.11

Compare Source

Patch Changes

• 5573bb0: bug fix: check ready before close
• 2372f39: Update submodule
• 4321a41: Fix premature ReadyForQuery responses after extended-query errors, preventing PostgreSQL clients from desynchronizing before Sync.

v0.5.10

Compare Source

Patch Changes

• 367ee2f: Bug fix: wait for running queries to finish before doing a data dir dump
• cb06c21: Wait for queries to finish before closing PGlite instance. See #​1128
• 78012ca: Fix a windowed live.query (one given offset and limit) leaking its live_query_<id>_get_total_count prepared statement on unsubscribe. Only live_query_<id>_get was deallocated, so the count statement survived every teardown while its backing view was dropped, accumulating dangling prepared statements for the lifetime of the database.

v0.5.9

Compare Source

Patch Changes

• 389b731: upgrade to PostgreSQL 18.6
• 389b731: Export additional core symbols from the main WASM module required by the plpgsql_check extension

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @nestjs/authentication@0.1.2
npm error Found: @electric-sql/pglite@0.5.14
npm error node_modules/@electric-sql/pglite
npm error   dev @electric-sql/pglite@"0.5.14" from the root project
npm error
npm error Could not resolve dependency:
npm error peer @electric-sql/pglite@"0.5.8" from @electric-sql/pglite-socket@0.2.11
npm error node_modules/@electric-sql/pglite-socket
npm error   dev @electric-sql/pglite-socket@"0.2.11" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-31T14_50_05_862Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-31T14_50_05_862Z-debug-0.log