-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can we reduce dependency count to make this actiually minimal ? Readme says minimal dependencies but actually has 165 dependencies which is absolutely insane. #48
Comments
The test package claims to have minimal dependencies but has 167 transitive dependencies because |
|
Oh wow i didn't know that, I've been using horrible horrible code for a while now const IS_DRY_RUN = process.argv.includes('--dry-run', 1);
// or
const maxSizeArg = argv.find(x => x.startsWith('--max-size='))
const maxSize = maxSizeArg && maxSizeArg.split('=')[1] |
Although The |
|
replaceAll exists Natively in Node.js 16+ which itself is soon EoL, we should just use the native versions probably. |
@juliangruber re |
This comment was marked as duplicate.
This comment was marked as duplicate.
Great, then I see a path towards this package having zero dependencies. which is exciting. |
@Raynos now would be a good time to say that PRs are welcome :) |
I'll open a PR if I get time or it becomes my problem. Right now my problem is that I use |
g
parameter. ( https://stackoverflow.com/a/17606289 ) there are alternative implementations that take 4 lines instead of 30 npm packages.readable-stream
; this seems excessive, it's a large package and a duplicate ofrequire('stream')
Leaving
minimist
as is seems ok, but I'd also inline all the argument parsing and go for zero dependencies. But at least I understand the purpose of it.The text was updated successfully, but these errors were encountered: