[3.4.1+] Setting port 3306 in createPool parameter will cause sveltekit project to break

[role-end]

I have a Sveltekit project with vite and running everything in deno. after updating version 3.4.1 or higher the project will break with

error: Uncaught (in worker "") (in promise) TypeError: Cannot read properties of undefined (reading 'Symbol(Deno.internal.rid)')
    at TCP.#read (ext:deno_node/internal_binding/stream_wrap.ts:227:45)
    at TCP.readStart (ext:deno_node/internal_binding/stream_wrap.ts:90:17)
    at _tryReadStart (node:net:404:30)
    at Socket.resume (node:net:838:7)
    at updateReadableListening (ext:deno_node/internal/streams/readable.js:1294:10)
    at processTicksAndRejections (ext:deno_node/_next_tick.ts:33:15)
    at runNextTicks (ext:deno_node/_next_tick.ts:76:3)
    at eventLoopTick (ext:core/01_core.js:185:21)

when using port 3306 for the connectionPool

this.pool = mariadb.createPool(
      {
        host: host,
        port: 3306,
        user: user,
        password: password,
        database: database,
      }
    );

With other ports like 2207 or 3308 there is no error during build.
I have also created a bug in the deno repository since I don't know where this has to be fixed.

denoland/deno#29945

In the meantime I can only rollback to 3.4.0 since it was the last working version.

[rusher]

Currently, only Node.js is officially supported. While Deno hasn't been tested yet, it's been on our roadmap as a desired feature. It appears now is the right time to pursue it.

[rusher]

issue reproduced with latest driver version:

error: (in promise) TypeError: Cannot read properties of undefined (reading 'Symbol(Deno.internal.rid)')
    at TCP.#read (ext:deno_node/internal_binding/stream_wrap.ts:231:45)
    at TCP.readStart (ext:deno_node/internal_binding/stream_wrap.ts:91:17)
    at _tryReadStart (node:net:404:30)
    at Socket.resume (node:net:838:7)
    at updateReadableListening (node:_stream_readable:1031:10)

I've read all changes with 3.4.0 and 3.4.1, but nothing is obvious.
i'll continue investigating

[rusher]

this will be handle properly with 3.5.0 version of the driver that will support deno