update API devDependencies [MRXN23-485] #1546
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hotzevzl
force-pushed
the
chore/api/MRXN23-485_upgrade-api-dev-dependencies
branch
from
adcfaa0 to
5006e38
Compare
yulia-bel
approved these changes
Oct 16, 2023
hotzevzl
deleted the
chore/api/MRXN23-485_upgrade-api-dev-dependencies
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://vizzuality.atlassian.net/browse/MRXN23-485
a little refresh to reduce some chances for sudden dependencymageddon close to wrapping up - I'm doing this just for the devDependencies as it's a lower risk upgrade
Even this, I've limited it a bit, since bumping past TypeScript v4.7 will cause a major collapse that involves typing yadda yadda in
nestjs-base-service, which I totally don't want to be dealing with at this stage.I did however use the force with Yarn, daring to upgrade from classic to v3, and thanks to FE's wise setup of the app's Dockerfile that seems to have gone ok too.