You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This isn't quite a "feature request" but you have no valid template I can use.
#26186 was abruptly closed without much explanation, so this is the issue to track the suggestion rather than jumping straight to a PR.
I'd like to suggest doing some general tidying of dependencies:
Remove any which are made redundant by native functionality
Remove any unmaintained dependencies that have widely used alternatives
Remove any oversized dependencies that have widely used alternatives
The reasons are generally as follows:
Increased supply chain security as there will be fewer dependencies, particularly fewer unmaintained dependencies
Decreased install size
Modernised dependencies (e.g. more ESM, less CJS)
Solution Brainstorm
Audit each of the monorepo's package.json for any dependencies that can be replaced. Ignoring opinionated switches for now, only focusing on those which are redundant, unmaintained, or oversized.
Additional Context
I spend a lot of my time working on widely used JS packages and tools to help improve the supply chain health. I've been doing this for many years across the ecosystem as a whole, and it'd be nice to apply some of that to sentry's packages too.
All of the suggestions/findings will result in a lighter weight package for both sentry maintainers and consumers, too.
Priority
React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it.
From my perspective, we'd replace one dependency that's somewhat in our control (@isaacs is part of our team) with a third-party dependency that isn't in our control. I appreciate the desire to help and reduce deps, rimraf is just not one of them.
would love to hear the reasoning for not doing this, if that's still your choice. it'll help me and other potential contributors better understand in case we ever approach this repo again.
Activity
linear-code commentedon Nov 6, 2026
JS-4083
andreiborza commentedon Nov 6, 2026
Hi @43081j, thanks for filing this.
From my perspective, we'd replace one dependency that's somewhat in our control (@isaacs is part of our team) with a third-party dependency that isn't in our control. I appreciate the desire to help and reduce deps, rimraf is just not one of them.
43081j commentedon Nov 6, 2026
fortunately, we can use
node:fsdirectly and still remove rimraf. Fully under your control, ~5 lines of code, no new dependency.would you still keep rimraf in that case?
here's the updated branch:
develop...43081j:sentry-javascript:jg/rimrafless
would love to hear the reasoning for not doing this, if that's still your choice. it'll help me and other potential contributors better understand in case we ever approach this repo again.