$ the-wire · showcase
commit-stream 3.0.0 locks imports to the package root
By RepoJournal · Filed · About Node.js · Composed from the cited sources · methodology
commit-stream's 3.0.0 adds types and package exports that cut off deep imports, and the same repo's dependency cleanup removes through2 and bl while its CI drops old Node.js release lines.
v3.0.0 nodejs/commit-stream
by github-actions[bot]
The exports field restricts imports to the package root, so any consumer reaching into internal paths (src/ or dist/ submodules) breaks on upgrade. Types now ship alongside, which is the reason the export map exists.
chore(deps): remove through2 and bl (#31) nodejs/commit-stream
through2 and bl are gone from the dependency tree, which matters if anything downstream relied on commit-stream's transitive copies of either, or if `npm dedupe` was relying on them existing at all.
chore(ci): drop old Node.js release lines (#32) nodejs/commit-stream
The CI matrix no longer tests old Node.js release lines, so fixes for those runtimes will stop being caught. Rod Vagg landed this alongside the dependency removal.
chore(release): 2.2.1 [skip ci] nodejs/commit-stream
The 2.2.1 patch accepts CVE IDs with four or more sequence digits, so longer CVE identifiers now parse; the same release migrates tests from tape to the node test runner.
feat: setup bundle workflow nodejs/microtel
The long tail: microtel set up a bundle workflow for node core integration and a benchmark-comparison job that runs a PR against its base branch and posts the delta on the GHA summary page, and branch-diff published 4.0.1 with only an actions/setup-node bump.
Action items
- → Replace any deep imports of nodejs/commit-stream subpaths before upgrading to 3.0.0 nodejs/commit-stream [plan]