-
Notifications
You must be signed in to change notification settings - Fork 1
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 Node v22 #1047
base: main
Are you sure you want to change the base?
Upgrade to Node v22 #1047
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actually, could you update the package.json required version as well?
EDIT: Hmm, we'll also want to update the Dockerfile as well.
EDIT 2: We'll also want to update the node version in the image. I'll give ya a call about that one.
|
@billhimmelsbach I still don't know what to do about the build of import-meta-env but things seem to be working as-is. It looks like the latest version of Node supported by |
Close #1040
Changes
View Institution Profile
that were missed as part of [View Institution profile] Update language #1013sbl_institution_types
isnull
or[]
.nvmrc
to usev22
package.json -> engines
to use Node v22node-js-alpine:3.20
base imageHow to test this PR
nvm use
yarn start
to easily launch all backend servicesyarn docker-build-and-run
to run the container version of the Frontend.env
file to run tests against the container versionyarn playwright test --workers 4