chore(deps): bump @electric-sql/pglite from 0.5.3 to 0.5.5

[dependabot]

Bumps @electric-sql/pglite from 0.5.3 to 0.5.5.

Release notes

Sourced from @​electric-sql/pglite's releases.

@​electric-sql/pglite-prepopulatedfs@​0.5.5

Patch Changes

• Updated dependencies [a290741]
• Updated dependencies [6b6f28d]
• Updated dependencies [354f4ae]
• Updated dependencies [219af1e]
• Updated dependencies [20839a7]
• Updated dependencies [7e784a4]
  • @​electric-sql/pglite@​0.5.5

@​electric-sql/pglite@​0.5.5

Patch Changes

• a290741: Reset retained protocol parser state after a malformed backend message so later queries can recover.
• 6b6f28d: Fix PGlite.create({ fs }) on a fresh database calling the provided filesystem's init() twice: the inner initdb instance no longer inherits the user-provided fs and always runs on its own scratch filesystem. Previously any VFS holding exclusive resources (e.g. OPFS sync access handles) failed with a contention error on first create.
• 354f4ae: Fix formatQuery (used by live.query/live.incrementalQuery to inline parameters) emitting %NL instead of the positional %N$L format specifier. A bare %NL is "min width N" and consumes format() arguments sequentially, so placeholders that are out of textual order silently bound the wrong values, and repeated placeholders failed with too few arguments for format().
• 219af1e: Expose the fields node-postgres derives from the CommandComplete command tag on Results: command (e.g. SELECT, INSERT, CREATE), and rowCount (the per-statement count from the tag). The tag was already received and parsed internally to compute affectedRows, but these values were not surfaced. Matching node-postgres' command/rowCount result fields lets pg-compatible adapters report them without re-parsing SQL.
• 20839a7: Preserve the host process.exitCode when closing a PGlite instance. close() calls _emscripten_force_exit(0), whose Emscripten runtime sets process.exitCode = 0, clobbering any exit code the host process had already set. This mirrors the existing save/restore guards in #init() and execProtocolRaw(), so closing a database no longer silently resets the host process's exit code.
• 7e784a4: Reject operations performed through transaction handles after the transaction has closed.

@​electric-sql/pglite@​0.5.4

Patch Changes

• 7e0d6d1: Detect the Node environment via process.type instead of process.versions.electron. The previous Electron guard (#951) also treated the Electron main and utility processes as non-Node, which broke PGlite's filesystem code path there. process.type only excludes Electron's web contexts (renderer, web worker, service worker), so PGlite keeps using the Node.js path in the Electron main and utility processes. Follow-up to #951 / #813.

@​electric-sql/pglite-prepopulatedfs@​0.5.4

Patch Changes

• Updated dependencies [7e0d6d1]
  • @​electric-sql/pglite@​0.5.4

Changelog

Sourced from @​electric-sql/pglite's changelog.

0.5.5

Patch Changes

• a290741: Reset retained protocol parser state after a malformed backend message so later queries can recover.
• 6b6f28d: Fix PGlite.create({ fs }) on a fresh database calling the provided filesystem's init() twice: the inner initdb instance no longer inherits the user-provided fs and always runs on its own scratch filesystem. Previously any VFS holding exclusive resources (e.g. OPFS sync access handles) failed with a contention error on first create.
• 354f4ae: Fix formatQuery (used by live.query/live.incrementalQuery to inline parameters) emitting %NL instead of the positional %N$L format specifier. A bare %NL is "min width N" and consumes format() arguments sequentially, so placeholders that are out of textual order silently bound the wrong values, and repeated placeholders failed with too few arguments for format().
• 219af1e: Expose the fields node-postgres derives from the CommandComplete command tag on Results: command (e.g. SELECT, INSERT, CREATE), and rowCount (the per-statement count from the tag). The tag was already received and parsed internally to compute affectedRows, but these values were not surfaced. Matching node-postgres' command/rowCount result fields lets pg-compatible adapters report them without re-parsing SQL.
• 20839a7: Preserve the host process.exitCode when closing a PGlite instance. close() calls _emscripten_force_exit(0), whose Emscripten runtime sets process.exitCode = 0, clobbering any exit code the host process had already set. This mirrors the existing save/restore guards in #init() and execProtocolRaw(), so closing a database no longer silently resets the host process's exit code.
• 7e784a4: Reject operations performed through transaction handles after the transaction has closed.

0.5.4

Patch Changes

• 7e0d6d1: Detect the Node environment via process.type instead of process.versions.electron. The previous Electron guard (#951) also treated the Electron main and utility processes as non-Node, which broke PGlite's filesystem code path there. process.type only excludes Electron's web contexts (renderer, web worker, service worker), so PGlite keeps using the Node.js path in the Electron main and utility processes. Follow-up to #951 / #813.

Commits

• 0ad2901 Version Packages (#1069)
• 219af1e node-postgres compat: add rowCount and command (#1067)
• 354f4ae fix: bind formatQuery params by position, not textual order (#1056)
• 6b6f28d fix: don't leak a user-provided fs into the inner initdb instance (#1060)
• 7e784a4 fix: reject operations on closed transaction handles (#1062)
• 20839a7 fix: preserve host process.exitCode when closing PGlite (#1059)
• 8b33b92 fix(live): resolve variable shadowing in unsubscribe callback filtering (#1051)
• 9dac42c Add moddatetime extension support (#1061)
• 25d0a55 Version Packages (#1044)
• 2dff2d2 fix(types): widen boolean serializer to accept number and string coercions (#...
• See full diff in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
good-wallet-v2	Ignored	Preview	Jul 30, 2026 5:38am