Upgrade dependencies to work with Node v22+ #14
Merged
Conversation
This file contains hidden or 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
Clears a high vuln in the older version.
to fix `yarn build` on Node 18+
Removes a bunch of transitive vulns
Use `resolutions` to pin transitive dependencies: - The `@types/react*` packages needed to be pinned to v17, else we'd get v19, which caused typing errors. - The rest needed to be pinned to avoid vulns.
Was previously failing with:
```
FAIL src/App.test.tsx
● Test suite failed to run
[BABEL] /home/work/code/fosdem-schedule-element-widget/src/setupTests.ts: Requires Babel "^7.22.0 || >8.0.0-alpha <8.0.0-beta", but was loaded with "7.12.3". If you are sure you have a compatible version of @babel/core, it is likely that something in your build process is loading the wrong version. Inspect the stack trace of this error to look for the first entry that doesn't mention "@babel/core" or "babel-core" to see what is calling Babel. (While processing: "/home/work/code/fosdem-schedule-element-widget/node_modules/@babel/plugin-syntax-import-attributes/lib/index.js")
at Object.assertVersion (node_modules/@babel/core/lib/config/helpers/config-api.js:74:15)
at builder (node_modules/@babel/plugin-syntax-import-attributes/src/index.ts:8:7)
at node_modules/@babel/helper-plugin-utils/src/index.ts:64:12
at node_modules/@babel/core/lib/config/full.js:211:14
at Function.<anonymous> (node_modules/@babel/core/lib/gensync-utils/async.js:26:3)
at evaluateSync (node_modules/gensync/index.js:251:28)
at cachedFunction (node_modules/@babel/core/lib/config/caching.js:68:46)
at cachedFunction.next (<anonymous>)
at loadPluginDescriptor (node_modules/@babel/core/lib/config/full.js:247:42)
at loadPluginDescriptor.next (<anonymous>)
at loadPluginDescriptors (node_modules/@babel/core/lib/config/full.js:158:30)
at loadPluginDescriptors.next (<anonymous>)
at node_modules/@babel/core/lib/config/full.js:186:21
at loadFullConfig (node_modules/@babel/core/lib/config/full.js:169:5)
at loadFullConfig.next (<anonymous>)
at transform (node_modules/@babel/core/lib/transform.js:25:45)
at transform.next (<anonymous>)
```
Required to fix the build.
reivilibre
approved these changes
Dec 24, 2025
reivilibre
left a comment
reivilibre
left a comment
There was a problem hiding this comment.
If it's tested to work in both dev & docker build, then I accept this, but the webpack config is virtually unreviewable to me. Mercifully it's just a build tool.
I find myself in awe at the amount of stuff needed to build a schedule widget 😅. If I was dealing with this more often I'd probably suggest switching to Vite, but it's not worth the hassle atm
You need to store the result in a variable before exporting it, apparently.
Prevent login from working during testing. It's possible this isn't added automatically anymore, or matrix.org just requires it now. Either way, needed to happen!
Member
Author
|
Tested after a node bump in the Dockerfile, and it looks good! 
|
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.
Fixes a bunch of flagged packages.
Codex CLI was used to do most of this. The only commit I don't fully understand is:
config/webpack.config.jsappears to be mainly updating to new config option namesconfig/webpackDevServer.config.jsappears to be mostly boilerplateRecommended to review commit-by-commit.