Conversation
Update all root and workspace package dependencies: - prettier 3.3 -> 3.8, rimraf 5 -> 6, lint-staged 15 -> 16 - @types/node 20 -> 25 (root, fuzzer, instrumentor) - cmake-js 7 -> 8, node-addon-api 7 -> 8 - yargs 17 -> 18 Yargs 18 is ESM-only, so its named exports like exit() are not accessible from CJS. Replace yargs.exit() with process.exit() in the CLI, which does the same thing. Swap out the ESLint 8 toolchain for ESLint 9 equivalents in package.json (config migration is in the next commit): - eslint-plugin-header -> eslint-plugin-headers - eslint-plugin-import -> eslint-plugin-import-x - @typescript-eslint/eslint-plugin -> typescript-eslint Add markdown-it override to 14.1.1 to fix a ReDoS vulnerability (GHSA-38c4-r59v-3vqw).
Replace .eslintrc.json and .eslintignore with a single
eslint.config.mjs using the new flat config format.
typescript-eslint v8 split ban-types into three rules:
- no-unsafe-function-type (for Function)
- no-wrapper-object-types (for Object, String, etc.)
- no-restricted-types (user-defined)
Update all inline eslint-disable directives to use the
new rule names. Fix one real Object -> object type issue
in transformerInterceptor.ts.
The old header/header plugin is gone; update 5 test files
to use the replacement headers/header-format directive.
Add *.fuzz.{js,ts} to the jest globals config, which the
old config covered via a global env setting.
Node 14-18 are all EOL. Update .nvmrc to v22 and set the root engine to Node >= 20 for development tooling (lint-staged 16 needs it for the /v regex flag). Published packages keep engines >= 14 for end users.
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.
No description provided.