chore(deps): upgrade node to 22 and do some cleaning#43
Merged
Conversation
DerekLimble
approved these changes
Mar 23, 2026
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
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.
Context
aligning limble-tree with the rest of the org's repos (webapp, flannel) on node 22. also took the opportunity to remove dead deps/scripts and patch vulnerable transitive deps.
Changes Made
.nvmrc→22.22package.jsonengines →node >=22.22 <23,npm >=10.9.4pullRequestChecks.yml) →node-version: "22"across all three jobseslint-watch,@angular-eslint/builderstartscript (broken in monorepo anyway,dev:sandboxis the real one)tarandserialize-javascriptto patch known vulnsng updateTesting Notes
npm cisucceeds on node 22npm run checkpasses (lint + format + build + tests)npm run dev:sandboxserves correctlynpm auditshows no high/critical vulns