-
Notifications
You must be signed in to change notification settings - Fork 115
Add support for @sentry/cli v2 #383
Conversation
|
This change will make |
|
@kamilogorek would it even though it's requiring one of v1 or v2 (ie Also node v8 is strongly outdated (https://github.com/nodejs/release#release-schedule) and many vendors have already moved to support node12 or newer as minimal node version and as you said sentry-cli itself is requiring newer version. Would that be a problem to upgrade so that all sentry tools are inlined on the same version of things? |
Great point - but at Sentry we aim to be as backwards compatible as possible. See: https://develop.sentry.dev/sdk/philosophy/#compatibility-is-king. Maybe it's fair to just drop Node support for the bundlers though. |
|
Tested the following: Yarn throws this error: npm installs So indeed package managers are not resolving package version based on the system node version/package's engine. With that said I was wondering if that would be possible to bump a new major (or minor? see bellow) version of this webpack plugin using the proposed version range ( That's a bit more of setup for people with node<12 but (without entering into a debate whether it's good or not to have outdated stuff) I believe that whoever is keeping their software stack up to date shouldn't have to pay for who is staying with old software. Side note - I have seen a few times the question of whether a dependency change should come with a major version bump - the question has generally been answered as "no" as their is no change in your public api |
Unfortunatelly yes. {
"name": "tmp",
"version": "1.0.0",
"main": "index.js",
"license": "MIT",
"dependencies": {
"@sentry/cli": "^1.74.5 || ^2.0.0"
}
}You can store it as |
That is true, as long as the dependency won't break the build, which in this case it does :( |
|
Is there anything we can do to get this merged? Old sentry/cli gives me |
|
We moved to |
Based on #362, it looks like this package supports the new major v2 release of @sentry/cli. However, it's still configured to only support v1 in the package.json. This is causing multiple versions of @sentry/cli to be installed in my project. This is a quick fix to allow the v2 version to satisfy the dependency and ensure that projects on the most up to date version don't install multiple versions.
Please let me know if there is anything else you need me to do here to get this merged!