-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
🏗️ Upgrade to Nuxt 3 #79
Merged
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
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.
Closes #36.
This PR upgrades the application from Nuxt 2 to 3 (and by proxy an upgrade from Vue 2 to 3).
As the migration documents note, "Nuxt 3 is a complete rewrite of Nuxt 2, and also based on a new set of underlying technologies." Hence, upgrading touched nearly every part of the application.1
Going granular on all of my changes would take me a long time, and I don't know that anyone is particularly keen on that level of detail; and much of it mirrors work in MapPacker on ConservationMetrics/map-packer#34.
However, what I would add is that this PR:
gc-shared-resources
library for things like middleware, components, auth.vitest
tests for most of the API server logic that relates to filtering or transforming data.What I'm not doing here:
Supporting building Docker images for arm in the Github workflows. Something about the refactor, or maybe the upgrade of the Docker image Node version, was breaking
arm64
,arm/v7
builds. So we'll have to figure that out later for Kakawa integration @luandro.Footnotes
I don't have the reference handy, but at some point I watched a video of a presentation by Evan You, the creator of Vue.js & Vite, where he described that upgrades moving forward will be much less painful, thankfully. ↩