This converts a number of comments in the code to JSDoc-style comments (and adds some more detailed descriptions/types along the way) and uses TypeScript to build type definition files from the comments. This allows you to publish types directly from this package instead of making TypeScript user install `@types/datadog-metrics`, which is maintained separately, by hand, and won't always be up-to-date.

It does not add new comments for objects that are not publicly exposed (although that would be a good idea for consistency). It also adds NPM lifecycle scripts to automatically build types when publishing.

Fixes #86.

This should help verify that most changes are valid.

This updates the syntax for all the public classes (reporters, BufferedMertricsLogger) to use native `class` syntax. This allows TypeScript to build better type definitions (compare the output before and after this commit). It also makes for slightly more compact and easy-to-manage syntax.

Partially fixes #83.

This extends the previous change to use class syntax and JSDoc comments everywhere in the codebase. It also turns on type checking (which now works because we are using class syntax everywhere).

The prepare script runs when installing, which causes errors when running tests, and means we see type errors multiple times over in CI. This moves it to prepack so it only runs when packing and/or publishing.

This probably shouldn't have gotten in originally, but it's pretty noisy when all tests run twice when pushing new commits to a PR (once for the push event and once for the update to the PR).

I missed adding release notes in #104, so I'm adding them separately here. This also cleans up some extra blank lines from that change.

Version 0.10.2 was just released with critical bugfixes, and this adds those updates to the `main` development branch (which has breaking changes and is focused on v0.11.0).

…100)

The `apiHost` property here is the same as what Datadog’s docs refer to `site`, so we’ve renamed it to match. We’ve also lower-cased the second "d" in `DatadogReporter`, since the previous spelling was wrong (see #59 and #98 for more about that).

Both of the old names still work, but using them prints deprecation warnings to let users know they should update their code.

The proposed feature in #107 was withdrawn because the problem it was solving could have already been handled with a custom reporter. This adds some documentation about how to set up a custom reporter to prevent similar misunderstandings in the future.

This is a follow-on to #104. I missed that this file would get published, even though it should not be.