Failure with Node.js 24

[darrachequesne]

Hi Marten! It seems there is an issue with Node.js 24:

$ nvm use 24
Now using node v24.9.0 (npm v11.6.0)

$ npm test

> @fails-components/webtransport-workspace@1.4.2 test
> npm run test:node && npm run test:node:http2 && npm run test:chromium && npm run test:chromium:http2:polyfill && npm run test:chromium:http2:ponyfill && npm run test:firefox:http2:polyfill && npm run test:firefox:http2:ponyfill && npm run test:webkit:http2:polyfill && npm run test:webkit:http2:ponyfill


> @fails-components/webtransport-workspace@1.4.2 test:node
> npm run test:node --workspace test


> @fails-components/webtransport-tests@1.4.2 test:node
> node index.js node http3

server ready


  bidirectional streams
free(): invalid pointer
Error cause mocha process Error: Command was killed with SIGABRT (Aborted): mocha --colors ./*.spec.js
    at makeError (file:///home/damien/git/socket.io/webtransport/node_modules/execa/lib/error.js:59:11)
    at handlePromise (file:///home/damien/git/socket.io/webtransport/node_modules/execa/index.js:119:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async runTests (file:///home/damien/git/socket.io/webtransport/test/index.js:76:5)
    at async file:///home/damien/git/socket.io/webtransport/test/index.js:127:3 {
  shortMessage: 'Command was killed with SIGABRT (Aborted): mocha --colors ./*.spec.js',
  command: 'mocha --colors ./*.spec.js',
  escapedCommand: 'mocha --colors "./*.spec.js"',
  exitCode: undefined,
  signal: 'SIGABRT',
  signalDescription: 'Aborted',
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}
npm error Lifecycle script `test:node` failed with error:
npm error code 1
npm error path /home/damien/git/socket.io/webtransport/test
npm error workspace @fails-components/webtransport-tests@1.4.2
npm error location /home/damien/git/socket.io/webtransport/test
npm error command failed
npm error command sh -c node index.js node http

Node.js 22 works fine though:

$ nvm use 22
Now using node v22.18.0 (npm v10.9.3)

$ npm test

> @fails-components/webtransport-workspace@1.4.2 test
> npm run test:node && npm run test:node:http2 && npm run test:chromium && npm run test:chromium:http2:polyfill && npm run test:chromium:http2:ponyfill && npm run test:firefox:http2:polyfill && npm run test:firefox:http2:ponyfill && npm run test:webkit:http2:polyfill && npm run test:webkit:http2:ponyfill


> @fails-components/webtransport-workspace@1.4.2 test:node
> npm run test:node --workspace test


> @fails-components/webtransport-tests@1.4.2 test:node
> node index.js node http3

server ready


  bidirectional streams
    ✔ sends and receives data over an outgoing bidirectional stream
    ✔ sends and receives data over an outgoing bidirectional stream including a zero length chunk
    ✔ sends and receives data over an outgoing bidirectional stream with big buffers
    ✔ sends and receives concurrently data over an outgoing bidirectional stream with big buffers (124ms
[...]

I haven't been able to pinpoint the issue, it seems the exception is not thrown in the JS scope.

[martenrichter]

Ok, I will try to reproduce it at weekend.
The trace is on which platform? (It may be a race condition, which behaves differently).

[darrachequesne]

Linux (Ubuntu 22)

[martenrichter]

I have just tested the local build for node24 (It was v24.10.0, though), and it did not crash (release and debug build). It was in a node:24-bookworm container, which is Debian-based, though it may differ from Ubuntu.

Did you build the plugin locally or use a prebuilt from a package? (Which version?) and is it current branch?

The error is a C++ error. The problem is that it can occur in many places
.
What happens if you run npm run oldtest ? (These tests are much simpler, and it may be easier to track where it crashes).
If it also crashes, can you please run it with: DEBUG=webtransport* npm run oldtest so that more debug output is included.

And if possible, can you add more log output to pinpoint which command crashes?

I assume this is a problem that occurs only at a specific timing, though it may be machine- and OS-dependent, and that it surfaces.

[darrachequesne]

I have upgraded to v24.10.0, but it does not seem to have any impact:

 $ node -v
v24.10.0

$ DEBUG=webtransport* DEBUG_TRACE=true npm run oldtest

> @fails-components/webtransport-workspace@1.4.2 oldtest
> npm run oldtest --workspace main


> @fails-components/webtransport@1.4.2 oldtest
> node old_test/test.js

  webtransport:native(205848) load webtransport binary: ../build/Release/webtransport.node +0ms
try connecting to server that does not exist
  webtransport:httpclient(205848):error quic connection timeout +0ms
  webtransportnode(205848) Connecting to unreliable failed: WebTransportError: Opening handshake failed.
    at Timeout.<anonymous> (file:///home/damien/git/socket.io/webtransport2/main/lib/client.js:68:11)
    at listOnTimeout (node:internal/timers:608:17)
    at process.processTimers (node:internal/timers:543:7) {
  Symbol(Symbol.toStringTag): 'WebTransportError'
} +0ms
  webtransportnode(205848) Now switching to reliable +1ms
  webtransport:http2:node:client(205848) http2 client error: Error: connect ECONNREFUSED 127.0.0.1:49823
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 49823
} +0ms
Did not connect to non-running server
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)
npm error Lifecycle script `oldtest` failed with error:
npm error code 134
npm error path /home/damien/git/socket.io/webtransport2/main
npm error workspace @fails-components/webtransport@1.4.2
npm error location /home/damien/git/socket.io/webtransport2/main
npm error command failed
npm error command sh -c node old_test/test.js

$ nvm use 22
Now using node v22.18.0 (npm v10.9.3)

$ DEBUG=webtransport* DEBUG_TRACE=true npm run oldtest

> @fails-components/webtransport-workspace@1.4.2 oldtest
> npm run oldtest --workspace main


> @fails-components/webtransport@1.4.2 oldtest
> node old_test/test.js

  webtransport:native(207557) load webtransport binary: ../build/Release/webtransport.node +0ms
try connecting to server that does not exist
  webtransport:httpclient(207557):error quic connection timeout +0ms
  webtransportnode(207557) Connecting to unreliable failed: WebTransportError: Opening handshake failed.
    at Timeout.<anonymous> (file:///home/damien/git/socket.io/webtransport2/main/lib/client.js:68:11)
    at listOnTimeout (node:internal/timers:588:17)
    at process.processTimers (node:internal/timers:523:7) {
  [Symbol(Symbol.toStringTag)]: 'WebTransportError'
} +0ms
  webtransportnode(207557) Now switching to reliable +1ms
  webtransport:http2:node:client(207557) http2 client error: Error: connect ECONNREFUSED 127.0.0.1:49823
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
  errno: -111,
  code: 'ECONNREFUSED',
  syscall: 'connect',
  address: '127.0.0.1',
  port: 49823
} +0ms
Did not connect to non-running server
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
got a newsession
server session is ready
install datagram echo
datagrams.writable is deprecated
client is ready
TEST 1: start
  webtransport:http3wtstream(207557):trace commitReadbuffer 3 +0ms
  webtransport:http3wtstream(207557):trace commitReadbuffer 3 +2ms
  webtransport:http3wtstream(207557):trace commitReadbuffer 3 +1ms
incoming bidi stream Uint8Array(3) [ 65, 66, 67 ] 1760392203398
  webtransport:http3wtstream(207557):trace commitReadbuffer 3 +3ms
incoming bidi stream Uint8Array(3) [ 68, 69, 70 ] 1760392203401
all bidi received, next close writer
  webtransport:http3wtstream(207557) callback streamFinal +0ms
  webtransport:http3wtstream(207557):trace networkfinish args { nettask: 'streamFinal' } +3ms
  webtransport:http3wtstream(207557) callback streamFinal +3ms
  webtransport:http3wtstream(207557):trace networkfinish args { nettask: 'streamFinal' } +4ms
  webtransport:http3wtstream(207557) callback streamFinal +1ms
  webtransport:http3wtstream(207557):trace networkfinish args { nettask: 'streamFinal' } +0ms
All data has been sent.
next close reader
All data has been read.
webtransport sending bidistream success
TEST 1: finish
[...]
now stop server
tests finished!
Server is gone

 $ uname -a
Linux home 5.15.0-157-generic #167-Ubuntu SMP Wed Sep 17 21:35:53 UTC 2025 x86_64 x86_64 x86_64 GNU/Linu

That's weird, the webtransport CI also seems to work fine with Node.js 24: https://github.com/socketio/webtransport/actions

I got an error in the socket.io CI, not sure if it could be related:

node: ../deps/v8/third_party/abseil-cpp/absl/hash/internal/low_level_hash.cc:51: uint64_t absl::hash_internal::LowLevelHashLenGt32(const void*, size_t, uint64_t, const uint64_t*): Assertion `len > 32' failed.
Aborted (core dumped)

Job: https://github.com/socketio/socket.io/actions/runs/18417799899/job/52485484935

[martenrichter]

I have upgraded to v24.10.0, but it does not seem to have any impact:

$ node -v
v24.10.0

I expected that it would not change, but to be sure.

$ DEBUG=webtransport* DEBUG_TRACE=true npm run oldtest

@fails-components/webtransport-workspace@1.4.2 oldtest
npm run oldtest --workspace main

@fails-components/webtransport@1.4.2 oldtest
node old_test/test.js

webtransport:native(205848) load webtransport binary: ../build/Release/webtransport.node +0ms
try connecting to server that does not exist
webtransport:httpclient(205848):error quic connection timeout +0ms
webtransportnode(205848) Connecting to unreliable failed: WebTransportError: Opening handshake failed.
at Timeout. (file:///home/damien/git/socket.io/webtransport2/main/lib/client.js:68:11)
at listOnTimeout (node:internal/timers:608:17)
at process.processTimers (node:internal/timers:543:7) {
Symbol(Symbol.toStringTag): 'WebTransportError'
} +0ms
webtransportnode(205848) Now switching to reliable +1ms
webtransport:http2:node:client(205848) http2 client error: Error: connect ECONNREFUSED 127.0.0.1:49823
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1637:16) {
errno: -111,
code: 'ECONNREFUSED',
syscall: 'connect',
address: '127.0.0.1',
port: 49823
} +0ms
Did not connect to non-running server
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)

Thanks, that is helpful!
Can you comment all lines between:
console.log('try connecting to server that does not exist')
and
console.log('start generating self signed certificate')

If my suspicion is correct, it will move the crash to a later point of the test (or no crash at all).

 $ uname -a
Linux home 5.15.0-157-generic #167-Ubuntu SMP Wed Sep 17 21:35:53 UTC 2025 x86_64 x86_64 x86_64 GNU/Linu

That's weird, the webtransport CI also seems to work fine with Node.js 24: https://github.com/socketio/webtransport/actions

No, it is not. I assume it is caused by a mistake that is triggered by the garbage collector when deleting one of the C++ objects. This can depend heavily on the timing of the individual machine, but if you cannot reproduce it, it is hard to debug.

I got an error in the socket.io CI, not sure if it could be related:

node: ../deps/v8/third_party/abseil-cpp/absl/hash/internal/low_level_hash.cc:51: uint64_t absl::hash_internal::LowLevelHashLenGt32(const void*, size_t, uint64_t, const uint64_t*): Assertion `len > 32' failed.
Aborted (core dumped)

Job: https://github.com/socketio/socket.io/actions/runs/18417799899/job/52485484935

Well, I think it is unrelated. It is also reported here (on a closed, unrelated issue):
#409 (comment)
but for nightly (which has lower priority than lts). It may be that it is a problem with the Abseil version and the version of quiche in the particular build.
As the test suggests, it may go away with newer library versions, so I do a release:

#418
but I do not think the other issue will go away. (or I hope not, as it will then only be hidden and wait that it can surface again).

[darrachequesne]

Commenting the lines here:

webtransport/main/old_test/test.js

Lines 31 to 49 in 6b499d7

	const badClient = new WebTransport('https://127.0.0.1:49823/echo', {
	serverCertificateHashes: [
	{
	algorithm: 'sha-256',
	value: Buffer.from(
	'a589bf4f98a0158aa890328d5d3f519b9e2a5b1e61b09eb10b7a9be0e79bf148',
	'hex'
	)
	}
	]
	})
	await Promise.all([badClient.ready, badClient.closed])
	.then(() => {
	console.error('Successfully connected to a non-running server?!')
	process.exit(1)
	})
	.catch(() => {
	console.log('Did not connect to non-running server')
	})

does not seem to have any impact:

 $ DEBUG=webtransport* DEBUG_TRACE=true npm run oldtest

> @fails-components/webtransport-workspace@1.4.2 oldtest
> npm run oldtest --workspace main


> @fails-components/webtransport@1.4.2 oldtest
> node old_test/test.js

  webtransport:native(222712) load webtransport binary: ../build/Release/webtransport.node +0ms
try connecting to server that does not exist
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)
npm error Lifecycle script `oldtest` failed with error:
npm error code 134
npm error path /home/damien/git/socket.io/webtransport/main
npm error workspace @fails-components/webtransport@1.4.2
npm error location /home/damien/git/socket.io/webtransport/main
npm error command failed
npm error command sh -c node old_test/test.js

The exception seems to be thrown at

webtransport/main/old_test/test.js

Line 112 in 6b499d7

await client.ready

Is there any way to get more logs?

[martenrichter]

Commenting the lines here:

webtransport/main/old_test/test.js

Lines 31 to 49 in 6b499d7
const badClient = new WebTransport('https://127.0.0.1:49823/echo', {
serverCertificateHashes: [
{
algorithm: 'sha-256',
value: Buffer.from(
'a589bf4f98a0158aa890328d5d3f519b9e2a5b1e61b09eb10b7a9be0e79bf148',
'hex'
)
}
]
})
await Promise.all([badClient.ready, badClient.closed])
.then(() => {
console.error('Successfully connected to a non-running server?!')
process.exit(1)
})
.catch(() => {
console.log('Did not connect to non-running server')
})
does not seem to have any impact:

$ DEBUG=webtransport* DEBUG_TRACE=true npm run oldest

Ok that is interesting, it rules out a crash in the client destructor.
It may be server side, as this code does not create anything at the server.

@fails-components/webtransport-workspace@1.4.2 oldtest
npm run oldtest --workspace main

@fails-components/webtransport@1.4.2 oldtest
node old_test/test.js

webtransport:native(222712) load webtransport binary: ../build/Release/webtransport.node +0ms
try connecting to server that does not exist
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)
npm error Lifecycle script oldtest failed with error:
npm error code 134
npm error path /home/damien/git/socket.io/webtransport/main
npm error workspace @fails-components/webtransport@1.4.2
npm error location /home/damien/git/socket.io/webtransport/main
npm error command failed
npm error command sh -c node old_test/test.js

The exception seems to be thrown at

webtransport/main/old_test/test.js

Line 112 in 6b499d7
await client.ready

May be, but it can be anywhere in the code, as it is called from the event loop. We only know when it happens. And it may be server side, but I am not sure.

Is there any way to get more logs?

If you build it manually, I usually place, printf("debug message\n);fflush(stdout); at crucial points in the C++ code to track the problem down. If you are willing to do this, I can try to figure out where to place messages.

[martenrichter]

I try again a new release to fix some the problems (last attempt failed in release CI due to an old version):
#419

[martenrichter]

Can you try the recent release 1.4.4 . It has newer libraries and I switched to Ubuntu 24 runners, as the older ones fail.

[darrachequesne]

Still no luck:

$ git log HEAD^1...HEAD
commit 3417276c2ef91b7364c030cab468d691b7f95698 (HEAD -> master, origin/master, origin/HEAD)
Author: Marten Richter <marten.richter@tu-berlin.de>
Date:   Tue Oct 14 17:46:16 2025 +0000

    1.4.4

$ node -v
v24.10.0

$ npm run oldtest

> @fails-components/webtransport-workspace@1.4.4 oldtest
> npm run oldtest --workspace main


> @fails-components/webtransport@1.4.4 oldtest
> node old_test/test.js

try connecting to server that does not exist
Did not connect to non-running server
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)
npm error Lifecycle script `oldtest` failed with error:
npm error code 134
npm error path /home/damien/git/socket.io/webtransport/main
npm error workspace @fails-components/webtransport@1.4.4
npm error location /home/damien/git/socket.io/webtransport/main
npm error command failed
npm error command sh -c node old_test/test.j

But there must be something wrong with my local environment, I can't even build the library locally:

 $ node build.js build
Webtransport binary handler: We are working on platform  linux_x64
Webtransport executed in dir: /home/damien/git/socket.io/webtransport/transports/http3-quiche
(node:16901) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use `node --trace-deprecation ...` to show where the warning was created)
[...]
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_chaos_protector.cc.o
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_coalesced_packet.cc.o
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_config.cc.o
/home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc: In member function ‘const QuicTagVector& quic::QuicConfig::ClientRequestedIndependentOptions(quic::Perspective) const’:
/home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc:570:34: error: the type ‘const QuicTagVector’ {aka ‘const std::vector<unsigned int>’} of ‘constexpr’ variable ‘no_options’ is not literal
  570 |   static constexpr QuicTagVector no_options;
      |                                  ^~~~~~~~~~
In file included from /usr/include/c++/11/vector:67,
                 from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/crypto/transport_parameters.h:11,
                 from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.h:14,
                 from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc:5:
/usr/include/c++/11/bits/stl_vector.h:389:11: note: ‘std::vector<unsigned int>’ is not literal because:
  389 |     class vector : protected _Vector_base<_Tp, _Alloc>
      |           ^~~~~~
/usr/include/c++/11/bits/stl_vector.h:389:11: note:   ‘std::vector<unsigned int>’ does not have ‘constexpr’ destructor
gmake[2]: *** [CMakeFiles/gquiche.dir/build.make:3684: CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_config.cc.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:814: CMakeFiles/gquiche.dir/all] Error 2
gmake: *** [Makefile:156: all] Error 2
ERR! OMG Process terminated: 2
child process exited with code 1
Building binary failed:  

[martenrichter]

Still no luck:

$ git log HEAD^1...HEAD
commit 3417276 (HEAD -> master, origin/master, origin/HEAD)
Author: Marten Richter marten.richter@tu-berlin.de
Date: Tue Oct 14 17:46:16 2025 +0000

1.4.4

$ node -v
v24.10.0

$ npm run oldtest

@fails-components/webtransport-workspace@1.4.4 oldtest
npm run oldtest --workspace main

@fails-components/webtransport@1.4.4 oldtest
node old_test/test.js

try connecting to server that does not exist
Did not connect to non-running server
start generating self signed certificate
start HttpServer and startup echo tests
server started now wait 2 seconds
now startup client
wait for client to be ready
free(): invalid pointer
Aborted (core dumped)
npm error Lifecycle script oldtest failed with error:
npm error code 134
npm error path /home/damien/git/socket.io/webtransport/main
npm error workspace @fails-components/webtransport@1.4.4
npm error location /home/damien/git/socket.io/webtransport/main
npm error command failed
npm error command sh -c node old_test/test.j

Ok, but the fix was more for the absl issue you also reported. (And of course an attempt).

But there must be something wrong with my local environment, I can't even build the library locally:

$ node build.js build
Webtransport binary handler: We are working on platform linux_x64
Webtransport executed in dir: /home/damien/git/socket.io/webtransport/transports/http3-quiche
(node:16901) [DEP0190] DeprecationWarning: Passing args to a child process with shell option true can lead to security vulnerabilities, as the arguments are not escaped, only concatenated.
(Use node --trace-deprecation ... to show where the warning was created)
[...]
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_chaos_protector.cc.o
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_coalesced_packet.cc.o
[ 91%] Building CXX object CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_config.cc.o
/home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc: In member function ‘const QuicTagVector& quic::QuicConfig::ClientRequestedIndependentOptions(quic::Perspective) const’:
/home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc:570:34: error: the type ‘const QuicTagVector’ {aka ‘const std::vector’} of ‘constexpr’ variable ‘no_options’ is not literal
570 | static constexpr QuicTagVector no_options;
| ^~~~~~~~~~
In file included from /usr/include/c++/11/vector:67,
from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/crypto/transport_parameters.h:11,
from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.h:14,
from /home/damien/git/socket.io/webtransport/transports/http3-quiche/third_party/quiche/quiche/quic/core/quic_config.cc:5:
/usr/include/c++/11/bits/stl_vector.h:389:11: note: ‘std::vector’ is not literal because:
389 | class vector : protected _Vector_base<_Tp, _Alloc>
| ^~~~~~
/usr/include/c++/11/bits/stl_vector.h:389:11: note: ‘std::vector’ does not have ‘constexpr’ destructor
gmake[2]: *** [CMakeFiles/gquiche.dir/build.make:3684: CMakeFiles/gquiche.dir/third_party/quiche/quiche/quic/core/quic_config.cc.o] Error 1
gmake[1]: *** [CMakeFiles/Makefile2:814: CMakeFiles/gquiche.dir/all] Error 2
gmake: *** [Makefile:156: all] Error 2
ERR! OMG Process terminated: 2
child process exited with code 1
Building binary failed:

I have seen this also during the release build (this is why 1.4.3 release failed, the arm runner had an older ubuntu image), it did not work on ubuntu 22 but an ubuntu 24 it worked. I assume that quiche now uses a feature, that the compiler on ubuntu 22 does not support.

[guest271314]

I'm getting these errors with your new build of webtransport.node on Debian 12 and node v25.0.0-nightly20251015170848bc18

$ node wt-server.js
Problem loading http3-quiche transport
Did you install @fails-components/webtransport-transport-http3-quiche?
http3 loader: Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /home/user/webtransport-js-bundle/webtransport.node)

bun wt-server.js
Problem loading http3-quiche transport
Did you install @fails-components/webtransport-transport-http3-quiche?
http3 loader: 949 |   wtpath = "./webtransport.node";
950 |   if (existsSync(path.join(dirname, buildpath + "/Debug/webtransport.node"))) {
951 |     wtpath = buildpath + "/Debug/webtransport.node";
952 |   }
953 |   log14("load webtransport binary:", wtpath);
954 |   wtrouter = require2(wtpath);
                   ^
error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /home/user/webtransport-js-bundle/webtransport.node)
 code: "ERR_DLOPEN_FAILED"

Using the webtransport.node file that I built locally, and that is 31.3 MB does work.

[guest271314]

This is how I built the working webtransport.node locally

git clone --recurse-submodules https://github.com/fails-components/webtransport.git
cd webtransport
CMAKEJS_PATH="$PWD/node_modules/.bin"
cd transports/http3-quiche
bun install
export PATH="$CMAKEJS_PATH:$PATH"
npm_config_yes=true bun x playwright install-deps
node build.js build
mv build_linux_x64/Release/webtransport.node webtransport-js-bundle
bun pm cache rm
cd ../..
rm -rf webtransport

[martenrichter]

I'm getting these errors with your new build of webtransport.node on Debian 12 and node v25.0.0-nightly20251015170848bc18

$ node wt-server.js
Problem loading http3-quiche transport
Did you install @fails-components/webtransport-transport-http3-quiche?
http3 loader: Error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /home/user/webtransport-js-bundle/webtransport.node)

bun wt-server.js
Problem loading http3-quiche transport
Did you install @fails-components/webtransport-transport-http3-quiche?
http3 loader: 949 |   wtpath = "./webtransport.node";
950 |   if (existsSync(path.join(dirname, buildpath + "/Debug/webtransport.node"))) {
951 |     wtpath = buildpath + "/Debug/webtransport.node";
952 |   }
953 |   log14("load webtransport binary:", wtpath);
954 |   wtrouter = require2(wtpath);
                   ^
error: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.38' not found (required by /home/user/webtransport-js-bundle/webtransport.node)
 code: "ERR_DLOPEN_FAILED"

Using the webtransport.node file that I built locally, and that is 31.3 MB does work.

This is caused by the update of the build runner to a newer ubuntu version. The older version did not compile anymore.
You have to update to debian 13.

[guest271314]

I don't have to update to Debian 13. I built your webtransport.node on Debian 12, locally.

The issue is your build process; gaps in between; not enough coverage.