Tobias Heldring

Looking closer at the code I realised there is an easy workaround ```typescript import feathersExpress from "@feathersjs/express" import { feathers } from "@feathersjs/feathers" import express from "express" import qs from...

This issue is blocking us from upgrading Typescript from 4 to 5 in our project currently. There is something really strange going on with the function overload matching. I tried...

We solved it in our project by using this class instead, with different order of function overloads for find ```typescript export class KnexServiceFixed< Result = any, Data = Partial, ServiceParams...

Can confirm we see the exact same issue and behaviour with a Azure SQL Database connection, Node 16.17.1, Tedious 15.1.1

Found that one can successfully catch and handle the error, and avoid the node process from crashing, by listening to the `error` event ```typescript connection.on("error", (error) => { console.error("Connection error",...

For others finding their way to this dead end, I can recommend going with a generic pool implementation like eg. https://github.com/coopernurse/node-pool. Well supported, promise based and with type definitions 👍