-
Notifications
You must be signed in to change notification settings - Fork 146
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
Support Node 20 (and drop Node 16) #1701
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.
Looks good, just a few minor requests.
And FWIW the lint script fails on me locally until I remove the import urlJoin
line in widget/src/ProvisioningApp.tsx
, so if the next CI run fails on that, it should be fixable.
Dockerfile
Outdated
RUN npm run build | ||
RUN npm prune --omit dev | ||
RUN yarn --strict-semver --frozen-lockfile | ||
RUN yarn build |
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.
I believe this is redundant since package.json
's "prepare"
step runs a build.
package.json
Outdated
@@ -5,7 +5,7 @@ | |||
"main": "app.js", | |||
"bin": "./bin/matrix-appservice-irc", | |||
"engines": { | |||
"node": ">=16" | |||
"node": ">=18" | |||
}, | |||
"scripts": { | |||
"prepare": "npm run build", |
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.
Can this (and other scripts) now use their yarn
equivalents?
Hmm, apparently the E2E tests fail non-deterministically...? |
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.
As long as:
- intermittent failures in the E2E CI tests are acceptable, and
- it's fine to no longer override the
matrix-bot-sdk
dependency only inm-a-b
's deps,
then this should be good to go.
See matrix-org/matrix-appservice-bridge#466.
This also moves us onto yarn, to be in line with the rest of our ecosystem.