feat(devtime): add minimum Node version metric - #414
Merged
Conversation
dreyfus92
marked this pull request as draft
August 28, 2026 15:03
dreyfus92
force-pushed
the
test/node-min-ver
branch
from
August 28, 2026 15:17
688a331 to
1ed2efe
Compare
dreyfus92
marked this pull request as ready for review
August 28, 2026 15:45
43081j
approved these changes
Aug 29, 2026
AlexanderKaran
approved these changes
Aug 29, 2026
Collaborator
|
Super nice work @dreyfus92 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
adds a "minimum node version" section to the dev time stats: the oldest node release that satisfies every
engines.noderange in a starter's installednode_modules, plus the starter's own manifest.the e18e's cli doesn't compute this, so it's done here for now, same pattern as the
core-jsand browser baseline scans. newrun:node-enginesscript in stats-generator, runs in the build job, merged bysave:ci-stats, validated invalidate-stats. ranges are resolved withverkit.the table also lists which packages set the floor, and there's a matching entry in the methodology page. values show up after the next stats run.
closes: #205