build: declare @types/node only in devDependencies - #27
Open
antobinary wants to merge 1 commit into
Open
Conversation
@types/node was listed in both dependencies and devDependencies, and the two had drifted apart before they were aligned on ^24.13.3. It supplies build-time typings only, so keep the devDependencies entry and drop the duplicate. npm already resolved it as a dev-only package, so installs are unaffected; this just makes package.json say what npm was already doing.
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
1 participant
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.
What
Drops the duplicate
@types/nodeentry fromdependencies, keeping the one indevDependencies.Why
@types/nodewas declared in both sections, and the two had drifted apart(
^20.3.1against^20.4.4) before they were aligned in the Node 24 PR. Itsupplies build-time typings only — nothing under
src/imports it at runtimeand it contributes nothing to the emitted bundle.
Neither CI nor
debian/rulesinstalls with--omit=devorNODE_ENV=production, so the typings remain present wherever the bundle isbuilt. npm already resolved it as a dev-only package, so installs are
unaffected; this just makes
package.jsonsay what npm was already doing.Testing
Against Node 24.20.0:
npm ci— PASSnpx tsc— PASSnpm run lint— PASSnpm run build-bundle— PASSNotes for review
One line out of
package.jsonplus the matching lock line. Depends on the Node24 PR and should merge after it.