chore: remove unused devDependencies - #508
Conversation
@jest/types was never imported: jest.config.ts takes Config from `jest` and the test suite uses @jest/globals. ts-node was only needed for Jest to load jest.config.ts. Node 24 strips types natively and Jest 30 relies on that, so it is dead weight.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #508 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 2 2
Lines 12 12
Branches 1 1
=========================================
Hits 12 12 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
There was a problem hiding this comment.
Pull request overview
This PR trims the project’s declared devDependency surface by removing @jest/types and ts-node from package.json, aligning the manifest with what’s directly imported/used in the repo while keeping the lockfile consistent with the updated dependency set.
Changes:
- Removed
@jest/typesfromdevDependencies. - Removed
ts-nodefromdevDependencies. - Regenerated
pnpm-lock.yamlto reflect the updated dependency graph.
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| package.json | Removes @jest/types and ts-node from declared devDependencies. |
| pnpm-lock.yaml | Updates the lockfile to reflect the dependency graph after removing the two devDependencies. |
Files not reviewed (1)
- pnpm-lock.yaml: Generated file
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Audited
package.jsonagainst actual usage across the sources, configs and workflows. Two devDependencies are dead weight:@jest/typesjest.config.tstakesConfigfromjest, andtests/index.spec.tsuses@jest/globalsts-nodejest.config.ts. Node 24 strips types natively and Jest 30 relies on thatEverything else is load-bearing and stays:
@swc/core(required peer of@swc/jest),@jest/globals,@swc/jest,jest,jest-junit(CI reporter),@tsconfig/node24,typescript,@types/node,xo+eslint-config-xo-bizon,tsdown,semantic-release+@bizon/semantic-release-config..github/dependabot.ymlneeds no change – thejestgroup's@jest/*pattern still matches@jest/globals.Verification
pnpm xo && pnpm check:ts && pnpm test && pnpm buildall pass: 7 tests, 100% coverage, dual CJS/ESM output builds as before.