Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
9.34.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
This is neither a bug, nor an issue.
Just a little problem caused by a particular version of rollup being pinned in the package dependencies
To reproduce a problem one just need to install @sentry/nextjs to an environment (repo or more likely monorepo) already using rollup. Quite likely it will cause package duplication, as latest version is always different. As long as rollup comes with a whole ecosystem, there will be many package duplicated.
Expected Result
@sentry/nextjs to use a "range" - for example "rollup": "^4.35.0", so it can "sync" and dedupe with potentially existing other version.
Actual Result
Both "rollup": "4.35.0"(sentry) and "rollup": "4.45.0"(current) will be pulled into a repo.
Is there an existing issue for this?
How do you use Sentry?
Sentry Saas (sentry.io)
Which SDK are you using?
@sentry/nextjs
SDK Version
9.34.0
Framework Version
No response
Link to Sentry event
No response
Reproduction Example/SDK Setup
No response
Steps to Reproduce
This is neither a bug, nor an issue.
Just a little problem caused by a particular version of rollup being pinned in the package dependencies
To reproduce a problem one just need to install
@sentry/nextjsto an environment (repo or more likely monorepo) already using rollup. Quite likely it will cause package duplication, as latest version is always different. As long as rollup comes with a whole ecosystem, there will be many package duplicated.Expected Result
@sentry/nextjsto use a "range" - for example"rollup": "^4.35.0", so it can "sync" and dedupe with potentially existing other version.Actual Result
Both
"rollup": "4.35.0"(sentry) and"rollup": "4.45.0"(current) will be pulled into a repo.