[0.3.6] Node (mac/linux) 21.x 22.x runtime error

[proutek]

After upgrade from 0.3.5 to 0.3.6 I'm not able to create instance of PGLite on Windows.
The same code works fine in WSL

I'm getting this message in command line.

RuntimeError: null function or function signature mismatch
❯ null. wasm:/wasm/02161842:1:401056
❯ null. wasm:/wasm/02161842:1:795603
❯ null. wasm:/wasm/02161842:1:547051
❯ null. wasm:/wasm/02161842:1:476800
❯ null. wasm:/wasm/02161842:1:332037
❯ null. wasm:/wasm/02161842:1:1575666
❯ null. wasm:/wasm/02161842:1:1365421
❯ null. wasm:/wasm/02161842:1:507474
❯ null. wasm:/wasm/02161842:1:2752803
❯ null. wasm:/wasm/02161842:1:3883116

I have tried it also without extensions. But it also throws this error.

[tdrz]

Hi @proutek thank you for this!

Could you please give us more details about your setup? Things like windows and node/browser version would be helpful...

[dbartholomae]

I'm running into the same error message on Mac M2.

[proutek]

Hi @proutek thank you for this!

Could you please give us more details about your setup? Things like windows and node/browser version would be helpful...

I'm running node 24.4.1 but I have tried also with 22.17.0 with same result.
I'm using pglite for e2e testing of my server app with vitest.

Wndows 10 Pro - 22H2 - Build 19045.6093

[tdrz]

I'm running into the same error message on Mac M2.

Which node version?

[dbartholomae]

Node v22.16.0

It works fine in our (default Linux) GitHub runner, but then didn't work when running locally. 0.3.5 works fine locally and on CI. I use this both for integration tests of our API and for e2e tests in the browser, and both fail, so it's not browser-specific.

[tdrz]

@dbartholomae I was unable to repro this on a Mac M1, do you have a full example that I could try that fails with that message on your machine?

[tdrz]

Also what would help us if anyone that can reproduce this would post the debug info when running PGlite with verbose debugging:

  const pg = await PGlite.create({
    debug: 5
})

[dbartholomae]

Here's the error in CI with debug logs:
https://github.com/dbartholomae/pglite-bug/actions/runs/16619742222

[dbartholomae]

It does actually work for that windows configuration, but not for that linux configuration. Or maybe it's flaky behaviour. The test I had written was slightly off, so here's the version where each failure comes from the error message mentioned above:
https://github.com/dbartholomae/pglite-bug/actions/runs/16619787005

[tdrz]

@dbartholomae Thank you, that's helpful!

Indeed, the windows test looks ok, just need to check the output differently.

Are you seeing this behavior also locally, or only on CI?

[dbartholomae]

For the reproduction repo, I see the same behavior locally. In the repo were I use this at work, I only see it locally, but we also don't run on all osses there.

[tdrz]

I've cloned that repo and run the test. They ran successfuly: https://github.com/tdrz/pglite-bug-749/actions/runs/16626190430/job/47043158241

Am I missing something?

[dbartholomae]

Weird. Unfortunately I don't know anything about database or operating system low-level operations, so I'm not sure I can be helpful to debug this. I've just rerun the tests again in my original repo and they consistently fail:
https://github.com/dbartholomae/pglite-bug/actions/runs/16626688311

Based on the commits between 03.5 and 0.3.6 I would assume that it's some change to how the bundling of wasm works that causes the problem, but unfortunately I don't know much about wasm either.