[dependabot]

Bumps @electric-sql/pglite from 0.5.11 to 0.5.14.

Release notes

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

@​electric-sql/pglite@​0.5.14

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

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

Patch Changes

• Updated dependencies [1cf7e86]
• Updated dependencies [48dd3fb]
• Updated dependencies [268929b]
  • @​electric-sql/pglite@​0.5.14

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

Patch Changes

• Updated dependencies [c7dc39e]
• Updated dependencies [8364675]
• Updated dependencies [a4cfd4d]
• Updated dependencies [2db5d2d]
  • @​electric-sql/pglite@​0.5.13

@​electric-sql/pglite@​0.5.13

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

@​electric-sql/pglite@​0.5.12

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.

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

Patch Changes

• Updated dependencies [0641b37]
• Updated dependencies [e752dbe]
• Updated dependencies [c31130c]
• Updated dependencies [0641b37]
  • @​electric-sql/pglite@​0.5.12

Changelog

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

0.5.14

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

0.5.13

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

0.5.12

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.

Commits

• 0974bdf Version Packages (#1176)
• 268929b Do not copy parsers (#1178)
• 48dd3fb initDb improvements (#1165)
• 1cf7e86 fix(pglite): only build asset URLs when PGlite loads the assets (#1175)
• a197da0 Version Packages (#1169)
• a4cfd4d Experiment: memfs2opfs (#1166)
• 8364675 Support for node-pg (#1171)
• c7dc39e fix(pglite): make close() wait for queries issued before it (#1170)
• 2db5d2d emsdk 6.0.5 (#1167)
• 02b1a41 Version Packages (#1157)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)