CI failed on older Node.js versions because of TypeError: debug.name.padEnd is not a function which is unrelated to this PR.

@Download, have you noticed this PR? I myself very often overlook some PRs/issues in my projects, so I’m better reminding…

Ehm... yes I did overlook it. Sorry!
I will keep a closer eye on things now that you are so active
And thanks again for your great contributions!

Is there a way to test this?

Or better yet... can we make it so that if the type defs go out-of-synch with the code, some test fails?
Because I am not using TS myself and I worry that I will not be able to keep these definitions in sync if there is no test that breaks when I mess it up

What is the status of this merge? The .d.ts file seems to work, and I'd like to use this in a Typescript program I'm working on.

What is the status of this merge?

I have to find some time to write tests for the type declarations.

@Download @jirutka Any news about when this PR will be merged?

@Download There is not much risk regarding the .d.ts definitions, it could break stuff if existing defs had existed, but because it's the first one, it won't.

Also, TS "bugs" are easily fixables using @ts-ignore and other tricks, it won't break existing production apps.

The easiest way to support TS is to build the package in TS, at least you're sure it won't be out of sync.

This could/should be merged quickly. Meanwhile, I'll manually add the d.ts file to my project.

See #33
I want this feature, but I want to 'do it right'.
Before, the betas simply weren't stable in the sense that everything kept changing... Now, I feel much more sure that it will only evolve from here and not change in revolutionary ways.