breaking: use parseArgs from Node 18.3+ instead of sade/mri
#2814
Closing issue
Description
We can drop multiple dependencies (sade/mri) from svelte-check when bumping engines to 18.3
Proposed solution
import { parseArgs } from 'node:util';
Alternatives
No response
Additional Information, eg. Screenshots
No response
Pull request
Draft
A
aewing Aug 6, 2025, 11:19 PM
- Replace sade dependency with Node.js built-in parseArgs from node:util
- Update engines requirement to Node.js >= 18.3.0 (when parseArgs was added)
- Remove sade and @types/sade dependencies
- Implement custom help and version handling to match original behavior
- Add proper TypeScript types for parseArgs options
Resolves #2521
Info
Assignees None
Reviewers None
Labels breaking change
Milestone None
A
aewing Aug 6, 2025, 11:23 PM@benmccann @jasonlyu123 let me know if you had something else in mind, happy to address any feedback.
D
dummdidumm Aug 14, 2025, 8:41 AM
Looks good, but we should only merge this once we cut a new svelte-check release. Putting it into draft mode to prevent accidental merges. Thank you!
👍 1
- Replace sade dependency with Node.js built-in parseArgs from node:util - Update engines requirement to Node.js >= 18.3.0 (when parseArgs was added) - Remove sade and @types/sade dependencies - Implement custom help and version handling to match original behavior - Add proper TypeScript types for parseArgs options Resolves #2521
Verified
packages/svelte-check/package.json +2 -4 6 changes
packages/svelte-check/src/options.ts +102 -75 177 changes
pnpm-lock.yaml -32 32 changes
Total
+104 -111