dbader / dbader/node-datadog-metrics
Consider dropping `@datadog/datadog-api-client`?
- Dominant language
- JavaScript
- Stars
- 147
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
One thing I’ve been thinking about is dropping our dependency on the official `@datadog/datadog-api-client` package. Folks value and use this package over that official one because of simplicity, and it is a pretty heavy-weight dependency for us to bring in. We don’t actually use much of its functionality or features, and it *mostly* serves as an HTTP client for us.
Would it be worth dropping this dependency and using the HTTP API directly? I currently plan to make a major, breaking release in January 2025 (see #131), and that might be a good time to upgrade the minimum Node.js version to 18, where `fetch` is built-in and we wouldn’t need to replace the Datadog client with anything at all.
This might not be worthwhile! It adds (a little) maintenance burden (mainly auth and error handling), and keeping a minimal dependency tree is probably not critical to most of our users here (if it is to you, please comment!).
Contributor guide
Assessment
This issue has not been assessed yet.