Skip to content

chore: bump dependency versions - #187

Open
BenjaminTruong-okta wants to merge 4 commits into
masterfrom
chore/modernize-toolchain-angular-21
Open

chore: bump dependency versions#187
BenjaminTruong-okta wants to merge 4 commits into
masterfrom
chore/modernize-toolchain-angular-21

Conversation

@BenjaminTruong-okta

@BenjaminTruong-okta BenjaminTruong-okta commented Aug 5, 2026

Copy link
Copy Markdown

Non-dependency changes

  • .husky/pre-commit: removed shebang/husky.sh sourcing line. Husky v7→v9 dropped this boilerplate.
  • package.json prepare script: yarn build → yarn build && husky. Husky v9 replaced husky install with a bare husky call.
  • angular.json: jest builder option configPath → config. Renamed in @angular-builders/jest v19→v21.
  • lib/.eslintrc.json: added "prefix": "okta" to a selector rule. Required explicitly by @angular-eslint/* v19→v21 (no longer
    defaulted).
  • scripts/setup-e2e.sh, scripts/setup.sh: node v22.16.0 → v22.18.0. Matches the Node engines bump in package.json.
  • util/maintain-banners.js: globby.sync() → named globbySync import. Globby v11→v16 dropped the default export/.sync() method
    (ESM-only now).

PR Checklist

Please check if your PR fulfills the following requirements:

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Adding Tests
  • Build related changes
  • CI related changes
  • Documentation changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Reviewers

@BenjaminTruong-okta BenjaminTruong-okta changed the title chore: modernize build/test toolchain to Angular 21 chore: bump dependency versions Aug 6, 2026
@BenjaminTruong-okta
BenjaminTruong-okta marked this pull request as ready for review August 6, 2026 18:06
Comment thread .husky/pre-commit
@@ -1,4 +1 @@
#!/bin/sh

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we can just remove husky. I can't find any reference to test:apps:clear - I think this is just leftover from an older approach

The pre-commit hook was inert on fresh clones/CI unless yarn install
re-ran the prepare script, and its git-add of test/apps/**/package.json
plus the already-dropped test:apps:clear call were leftovers from the
old yalc-based test-app linking flow removed in df93feb.
Comment thread package.json Outdated
},
"engines": {
"node": ">=22.16.0",
"node": ">=22.18.0",

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you remove this? This would be considered a breaking change. If you need to specify a specific version of node for building, use https://docs.npmjs.com/cli/v11/configuring-npm/package-json#devengines. engines requires a specific version of node to install the package and therefore could break customer builds

… bump

Revert @babel/* in test/e2e to ^7.x; the 7->8 bump was the only thing
requiring Node >=22.18.0, and it was not otherwise necessary. Node
requirement reverts to >=22.16.0. Also switch root engines to
devEngines per review comment, since engines on a published package
can break customer installs.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants