chore: convert src/logging.{js,ts}

[bkeepers]

As a way of getting familiar with the SignalK internals, I'm working on converting some of the remaining code to TypeScript. This converts src/logging.js to TypeScript.

[tkurki]

Would it make sense to compile a single PR instead of PR per each file? Do you have a plan of attack for the other files?

[bkeepers]

Would it make sense to compile a single PR instead of PR per each file? Do you have a plan of attack for the other files?

Sure I can batch some together if you prefer. I don't really have a plan besides ls -Sr src/**/*.js to get the list of files remaining sorted smallest to largest and started on the first one I saw that didn't have other dependencies, but I can put together a little more of a plan and do a larger chunk.

[bkeepers]

Also, I converted the signalk-tides plugin to TypeScript and ran into a lot of challenges that I plan to open PRs to address: bkeepers/signalk-tides#2

[rhbvkleef]

Why aren't you doing function (...args: Parameters<typeof errWrite>) here? Similarly for outWrite.

[bkeepers]

write is an overloaded function in typescript, and Parameters<typeof errWrite> only returns the first function signature, which results in a TypeScript error. See microsoft/TypeScript#32164 for more on this issue.

The ideal solution here is probably to do something like process.stderr = new Transform() { … } and piping that to the old stderr instead of just overwriting the write method, but I didn't want to make too invasive of changes here.

[bkeepers]

Would it make sense to compile a single PR instead of PR per each file? Do you have a plan of attack for the other files?

@tkurki I started working on batching a bunch of these together, but it started to feel like I am trying to boil the ocean. #1947 and #1948 were the result of some of this work. To avoid opening massive PRs like that, I think I'd prefer to keep these small and focused.