Could @sentry/remix have a broader version range for @sentry/cli

[tmcw]

I've been trying to avoid the "gigantic node_modules problem" in my projects, and Sentry's often one of the major ones. Right now what i'm seeing is that in this project I have @sentry/remix installed to instrument remix, and @sentry/cli installed to push new releases. However, sentry/remix pins its dependency on sentry/cli:

https://github.com/getsentry/sentry-javascript/blob/develop/packages/remix/package.json#L30

To an out-of-date version (this one's about 3 months old). So I get copies of @sentry/cli. And sentry/cli is a gigantic package - it's 27MB:

$ du -sh node_modules/@sentry/cli
 27M	node_modules/@sentry/cli

This is kind of unfortunate, and my questions are:

• Why does sentry/remix depend on sentry/cli anyway?
• Could it pin the most recent version? Or re-expose the binaries from sentry/cli?

[AbhiPrasad]

Why does sentry/remix depend on sentry/cli anyway

The Remix SDK depends on sentry cli to make the upload-sourcemaps script exposed by the remix sdk work.

We should bump the CLI version though, I'll take care of that.

[AbhiPrasad]

Actually I realized your question was if sentry-cli should have a broader version. I think the answer here is yes, will make that change instead.

[AbhiPrasad]

#9401

[tmcw]

Thanks! Works like a charm, saves us 39mb in node_modules 👏