Open anoblet opened 11 months ago
Hmm, I was thinking maybe v23 latest point release is safer, but I think we can also evaluate now whether everything still works in v24?
I remember I had some breaking changes concerns, but can't recall exactly what they were :thinking: we need to investigate v24 changelog.
Taking smaller steps would probably be better. I'm curious, running yarn upgrade-interactive --scope '@vaadin'
only updates package-lock.json
and not package.json
. Is this something we're comfortable with? It feels a bit unnatural to search and replace package versions for no effect.
I'm curious, running
yarn upgrade-interactive --scope '@vaadin'
only updatespackage-lock.json
and notpackage.json
. Is this something we're comfortable with? It feels a bit unnatural to search and replace package versions for no effect.
This is referring to minor version upgrade? If constraints listed in package.json
remains valid, I don't see a problem. What yarn
version are you working with? This behavior may have changed over time?
This is referring to a minor upgrade. I'm using the latest version of yarn (1.22.19), and this looks to be expected behavior: https://dev.to/wgao19/why-running-yarn-upgrade-does-not-update-my-package-json-3mon
It's a bit confusing, though I don't see a need to update constraints.
size-limit report 📦