refactor: migrate to typescript, undici, and improve contributing

[semoal]

Hi guys, hope this pull-request suits you well

I've had a boring weekend and had time to give some love to this library, QuestDb is cool but db clients experience must be a requirement for you as a company, so since it's open-source I'm happy to collaborate with you 🤟

What's new?

• From npm to pnpm for installing dependencies, much faster and stable, more common in JavaScript ecosystem lately.
• Eslint 9.x with better defaults, also added Prettier to handle style-guide.
• Migrate the entire source-code to Typescript, I've removed ALL anys and everything is type-safe.
• Bunchee for compiling the library, this emits the dual-cjs approach that is complicated to generate, now we're compatible with esm and cjs without any problems, also the typings are auto-generated.
• Migrated from Jest to Vitest, much more maintained, faster and has a lot of features that are super-useful for testing.
• Upgraded JSDoc and regenerated the documentation site.
• Added a CONTRIBUTING.md guide for making it easier to collaborate and introduce new features.

Breaking changes

• Drop non-LTS version of Node, now we're compatible from Node 20 or greater, this is also tested on the matrix Github workflow testing suite.
• http.Agent and http.Agents are cool, but latest Node version ship with a library called Undici which is by far better, easier to handle retry, faster, and more maintained and its core contributors are Node maintainers.

Performance improvements

Getting rid of http.agent and using Undici made that when I've installed the library in my project and run some benchmarks creating 2M rows in 64 iterations with a time limit of 5000ms of run we had a nice result:

┌─────────┬───────────┬────────────────────────┬───────────────────────────┬────────────────────────────┬───────────────────────────┬─────────┐
│ (index) │ Task name │ Latency average (ns)   │ Latency median (ns)       │ Throughput average (ops/s) │ Throughput median (ops/s) │ Samples │
├─────────┼───────────┼────────────────────────┼───────────────────────────┼────────────────────────────┼───────────────────────────┼─────────┤
│ 0       │ 'v4.0.0'  │ '54626798.72 ± 27.37%' │ '43224916.50 ± 17958.50'  │ '22 ± 3.08%'               │ '23'                      │ 106     │
│ 1       │ 'v3.0.0'  │ '63162652.05 ± 5.29%'  │ '59678416.50 ± 291166.50' │ '16 ± 2.81%'               │ '17'                      │ 80      │
└─────────┴───────────┴────────────────────────┴───────────────────────────┴────────────────────────────┴───────────────────────────┴─────────┘

1. Latency (average):

   • v4.0.0 achieves a ~14% reduction in average latency, indicating faster performance.

2. Latency (median):

   • v4.0.0 shows a significant improvement in median latency, reducing it by ~28%.

3. Throughput (average):

   • Throughput increased by ~37.5% in v4.0.0.

4. Throughput (median):

   • v4.0.0 delivers a ~35% improvement in median throughput.

---

Summary of Improvements

• Substantial reduction in both average and median latency (~14% and ~28%, respectively).
• Significant increase in both average and median throughput (~37.5% and ~35%, respectively).
• Overall, v4.0.0 demonstrates superior performance and efficiency compared to v3.0.0.

These results confirm the improvements introduced in v4.0.0, making it a faster and more capable version.

[CLAassistant]

All committers have signed the CLA.

[woss]

Excellent PR!

I have left a few comments.

[semoal]

@puzpuzpuz @glasstiger a cool review here would be super nice:) sorry for pinging just want to move this forward

[nwoolmer]

Hi @semoal ,

Thanks for the contribution!

Do you know if this resolves your socket issue, or is this an ongoing problem?

#40

[semoal]

Hi @semoal ,

Thanks for the contribution!

Do you know if this resolves your socket issue, or is this an ongoing problem?

#40

Yes, it does. Undici handles way better the connection under the hood

[puzpuzpuz]

Wow, that's a biggish PR! We may need some time to review it, so please keep this in mind.

[semoal]

Wow, that's a biggish PR! We may need some time to review it, so please keep this in mind.

Yes, no hurry from my side, we forked internally and using it already in production, just wanted to ping to make sure that you're "subscribed" to this repo :)

[semoal]

To make you a real demo, I've reviewed some heavy load (it's bandwidth coming through our production QuestDB machine):

• The initial peak of this graph generated the error socket: hang out without the new version, from 400K jobs easily 15k were failed because socket hang out
• The latest peak, was handled with the new version (v4.0.0) , 0 errors, 90% cpu and handled without any problems the connection.

This demonstrates how well Undici manages connection pooling under the hood and how fast it is, easily managed a throughput of 2x or 3x, we were limited to run our asynchronous pipelines to 15 machines because this error, and with the new version we put 100 machines at the same time, and went amazingly good.