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.
I've updated all pending dependencies used by the dashboard, excepting
@types/node
which we still want to mantain on v20.x because we haven't upgrade to Node.js 22 yet.For the record, the process I follow looks as follows:
npm run deps
(mentioned here) which launches an interactive user interface listing available updates,npm run build
) and test (npm run test
); confirm it works - if changes are required in our codebase, I launch vitest withnpx vitest dev
to watch the code and run the tests automatically while I make the necessary updates. Often I need to read the release notes, look up breaking changes, etc.npx prettier . --write
to fix.During the upgrade, I've had to dealt with the following issues:
Silenced a new build warning (via
vite.config.ts
) related to the use of mixed declarations in Bootstrap. I've seen that this is being addressed in Bootstrap v5.3.4 but it has not been released yet.Dealt with some minor and well documented backward-incompatible changes introduced by v0.9 and v0.10. Also, we haven't adopted data loaders yet (added in v0.8), which is an interesting feature we should probably explore.
Updated
UUID.test.ts
to mockdocument.execCommand('copy')
which is the fallback mechanism to interact with the clipboard (seeuseClipboard
for more details). I couldn't figure out how to fake the navigator permission instead - added a TODO note.Fixes #1021.