fix: replace latest-version
with a single fetch request
#1217
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since we don't configure any private registries or authentication, we don't need the
latest-version
dependency that pulls in 16 additional packages for features we don't use. Engines declares node 22.16.0 and fetch became stable around ~21-ish.Using fast-npm-meta by antfu is a matter of preference. I like it more as it provides basic caching - alternatively, we can make a direct request to https://registry.npmjs.org/@sentry/core/latest which has a slightly larger payload but eliminates any external service dependency.
UPD: npm's rate limiting is described here and it's generous imo https://docs.npmjs.com/policies/open-source-terms#acceptable-use (see number 17).