Linting and Formatting Release Notes

Release notes for code linting, formatting and type-checking tools

Get this feed:

Products (5)

Latest Linting and Formatting Updates

Jul 16, 2026
Date parsed from source:
Jul 16, 2026

First seen by Releasebot:
Jul 17, 2026
Eslint

Automating ESLint migrations with Codemod

Eslint releases official Codemod-powered migration tools for v8 to v9 and v9 to v10 upgrades, giving users new codemods for config, custom rules, RuleTester, and API updates while still flagging some manual review steps.
ESLint and Codemod are partnering to deliver official codemods for ESLint migrations.

We are excited to announce a partnership between ESLint and Codemod to create a better migration experience for ESLint users, starting with the ESLint v8 to v9 and v9 to v10 migrations. All official ESLint codemods live in eslint/codemods and on the Codemod Registry. Community members are encouraged to open issues for missing codemods or contribute new ones through pull requests. Once reviewed and merged by maintainers, codemods are automatically published to the Codemod Registry through GitHub Actions.

What is Codemod?

Codemod is an open source platform for building, sharing, and running automated code migrations at scale. It is an OpenJS Foundation partner, and its tooling has been adopted by projects such as React, Node.js, Express, React Router, Nuxt.js, pnpm, Webpack, MSW, i18next, and more.

Its platform includes JSSG (JS ast-grep), a codemod runtime and workflow engine that supports multi-step transformations and combines deterministic, compiler-aware transformations with AI-powered steps to deliver the right balance of reliability, efficiency, and flexibility. The source code for the Codemod CLI and engine is available on GitHub.

Key features of Codemod include:

Workspace-wide semantic analysis

Cross-file refactors

Multi-language support

Repository-scale performance

A simple, agent-friendly API

Built-in AST inspection through MCP

Secure sandboxed execution

Metrics and codebase mining

Native support for multi-file transformations

Check out the Codemod docs to learn more about JSSG (JS ast-grep), Codemod’s open source toolkit for building codemods, and explore its features.

ESLint v8 to v9 migration

For v8 to v9 migration, we’ve released two codemods: one to help upgrade ESLint config, and another for custom rules.

Migrating configuration with @eslint/v8-to-v9-config

npx codemod @eslint/v8-to-v9-config

Unlike the original ESLint Configuration Migrator, this codemod runs as a workspace migration. It can:

Extract eslintConfig from package.json and generate eslint.config.mjs

Clean up duplicate /* eslint / comments and invalid / exported */ comments in source files

Remove deprecated require-jsdoc and valid-jsdoc rule references from inline comments

Migrate those JSDoc rules to eslint-plugin-jsdoc using jsdoc({ config: "flat/recommended", ... })

Add a // TODO: Migrate settings manually comment when custom settings need review

Handle several ESLint v9 rule option changes, including no-unused-vars, no-useless-computed-key, no-sequences, no-constructor-return, camelcase, and no-restricted-imports

Convert env to languageOptions.globals using the globals package

Map excludedFiles to per-config ignores

Move noInlineConfig and reportUnusedDisableDirectives to linterOptions

Import parser packages and plugins

Use defineConfig and globalIgnores from @eslint/config-helpers

Merge ignore patterns from both .eslintignore and .gitignore

For JavaScript config files, the codemod works from the AST and can resolve simple bindings such as const values, identifiers, and spreads. More advanced logic, such as functions, conditionals, and dynamic require() calls, still needs manual review. The workflow also supports options such as --target, eslintConfigCustomName, and codeFormattingCommandEnabled, and prompts you to install required packages after it runs.

The codemod does not migrate --ext CLI usage, so you still need to create a config entry for the file extensions you previously passed on the command line. Learn more on @eslint/v8-to-v9-config’s registry page and in the configuration migration guide.

Migrating custom rules with @eslint/v8-to-v9-custom-rules

npx codemod @eslint/v8-to-v9-custom-rules

Important: Run this codemod only in directories containing ESLint rule files. It may incorrectly transform other JavaScript files that export functions.

The codemod supports CommonJS (module.exports = function (context) { ... }), ES Modules (export default function (context) { ... }), indirect exports (function rule() {} and module.exports = rule), higher-order wrappers such as wrapRule(function (context) { ... }), and rules created with @typescript-eslint/utils.RuleCreator.

It performs a comprehensive migration of custom ESLint rules from v8 to v9, including:

Removed context methods — migrates calls to sourceCode equivalents (for example, context.getSource() → sourceCode.getText()), including methods that moved with different signatures such as getScope(), getAncestors(), getDeclaredVariables(), and markVariableAsUsed()

context methods becoming properties — migrates getSourceCode(), getFilename(), getPhysicalFilename(), and getCwd() to their property equivalents with compatibility fallbacks

Removed context.getComments() — converts node-specific calls to getCommentsBefore / getCommentsInside / getCommentsAfter(node)

Removed CodePath#currentSegments — adds code path tracking logic (verify the result matches your rule’s needs)

Function-style rules are no longer supported — converts to the object format with meta and create

The codemod also moves module.exports.schema into meta, converts old-style context.report(node, message) calls to object format, detects fixable rules, and adds fixable: "code" to meta.

It does not cover context.parserOptions and context.parserPath, because those properties are not removed until ESLint v10.0.0. Prefer context.languageOptions (and context.languageOptions.parser when you need the parser) instead.

Not every change can be fully automated. After running the codemod:

Review TODO comments. Search for TODO in your migrated files. If a rule uses context.options, the codemod may leave a placeholder like schema: [] // TODO: Define schema - this rule uses context.options that you need to replace with a valid JSON schema.

Review comment method changes. getCommentsBefore(), getCommentsInside(), and getCommentsAfter() require a node argument, and no-argument context.getComments() calls should use sourceCode.getAllComments().

Review skipped higher-order wrappers. If a wrapper passes configuration as the second argument (for example, wrapRule(rule, config)), confirm whether any manual migration is needed.

Test your custom rules by running your rule test suite (for example, npm test).

Learn more on @eslint/v8-to-v9-custom-rules’s registry page. For the full list of API changes and how to adopt them manually, see the ESLint v9 migration guide and the blog post for v9 custom rules.

ESLint v9 to v10 migration

Upgrade your ESLint project from v9 to v10 with the following codemod:

npx codemod @eslint/v9-to-v10

This recipe includes four individual codemods, each of which can also be run independently:

@eslint/v9-to-v10-config: Remove legacy env vars and CLI flags

@eslint/v9-to-v10-custom-rules: Replace removed context and SourceCode methods

@eslint/v9-to-v10-ruletester: Cleanup RuleTester test cases

@eslint/v9-to-v10-linter-api: Fix Linter/ESLint API usage

Check out Codemod Registry to learn more about this recipe and its codemods. For more details about what’s new in v10 and how to adopt the new features, refer to the official ESLint upgrade guide.

Conclusion

Upgrading across major ESLint versions has often meant carefully translating configs, custom rules, and related APIs by hand. With this partnership, official Codemod workflows give you a faster starting point for the v8 to v9 and v9 to v10 migrations, while still leaving room for the manual review steps that complex projects need.

You can try the codemods today through the Codemod Registry, and find the source in eslint/codemods. If you run into a gap, open an issue or contribute a new codemod. For questions about the migrations themselves, see the v9 and v10 upgrade guides, or stop by Discord to talk with the team.
Original source
Jul 14, 2026
Date parsed from source:
Jul 14, 2026

First seen by Releasebot:
Jul 15, 2026
Oxc

oxlint_v1.74.0: release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)

Oxc releases linter and formatter updates with new namespace and .mts config support, autofix for import duplicates, and many bug fixes plus performance improvements across oxlint and oxfmt.

Oxlint

🚀 Features

0433a83 linter/eslint/no-inner-declarations: Add namespaces option (#24044) (Boshen)
92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)
8c1d74b linter/import/no-duplicates: Add autofix logic (#24273) (Cole Ellison)

🐛 Bug Fixes

0b086de linter/jest/prefer-lowercase-title: False positive when lowercaseFirstCharacterOnly is false (#24414) (Connor Shea)
097cb95 linter: Allow vite-plus/test and `@effect as Vitest source (#24196) (Liang)
8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)
9ba30e5 linter/oxc/bad-replace-all-arg: Add note to enhance diagnostic (#24346) (camc314)
2ce5a33 linter: Resolve ignorePatterns relative to the config dir (#24339) (leaysgur)
ab90eed linter/eslint/no-loop-func: Do not error on catch variables (#24316) (Chris Opperwall)
b67f0a6 linter/eslint/no-unused-vars: Count default parameter updates as usage (#24323) (camc314)
d193f8e linter: Detect Junie agent env vars (#24277) (Jeevan Mohan Pawar)
2aecf60 linter/eslint/no-unreachable: Handle break in switch stmts correctly (#24260) (camc314)

⚡ Performance

7f80cac linter/vue/prop-name-casing: Precompile ignoreProps regex pattern (#24413) (connorshea)
6272051 linter/typescript/no-require-imports: Compile allow patterns once (#24417) (connorshea)
fb1edf1 linter: Compute comment fix span only for directive comments (#24419) (connorshea)
33805b9 linter/jsdoc/require-param: Compile checkTypesPattern regex once (#24420) (connorshea)
8de6fca linter/jest/valid-title: Compile disallowedWords regex once (#24412) (Connor Shea)
4a0d8dc linter/eslint/no-underscore-dangle: Avoid String clone per identifier (#24371) (Ian Macalinao)
f3ab04c linter/typescript/consistent-type-imports: Remove redundant Vec per violation (#24370) (Ian Macalinao)
4d2d78d linter/typescript/prefer-ts-expect-error: Avoid String clone per comment (#24369) (Ian Macalinao)

Oxfmt

🚀 Features

3a7fe74 formatter_css: Update oxc-css-parser to 0.0.7 (#24434) (leaysgur)
0173cd3 formatter_css: Format Less :extend and merge props (#24358) (leaysgur)
92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)
df250df formatter: Support quoteProps for TS enum and methods (#24309) (leaysgur)
a9a5cd6 formatter_core: Expose SourceText::as_str() (#24281) (leaysgur)

🐛 Bug Fixes

162bddf formatter: Add required parens for conditional type in type parameter constraint (#24450) (leaysgur)
2d22a91 formatter: Determine type cast target from span instead of lexical scan (#24447) (leaysgur)
25306e9 formatter: Do not add extra parens with type cast comment (#24444) (leaysgur)
bd6edfe formatter: Break arrow signature that exactly fills the line when cond body may hug (#24440) (leaysgur)
a99ef41 formatter: Keep quotes on method signature named new (#24432) (leaysgur)
fcc28df formatter_css: Keep glued-braket-value tight (#24352) (leaysgur)
8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)
b7c7e15 formatter: Add parens for import and private field in new callee chain (#24320) (leaysgur)
0c8f6e4 formatter: Update detect_code_removal for #24309 (#24314) (leaysgur)
a85aad0 formatter: Fix member-chain and non-null parens (#24312) (leaysgur)
1c29c73 formatter: Preserve TSNonNullExpression in chain expression (#24311) (leaysgur)
8933c0e formatter: Keep comment inside of empty switch block (#24308) (leaysgur)
ec26af2 formatter: Preserve blank lines between JSX attrs (#24290) (leaysgur)
70bd54d formatter: Keep arrow function body comment (#24287) (leaysgur)
415fe1e oxfmt: Error on ignorePatterns that cannot match files outside the config directory (#24286) (leaysgur)
eeabc4a formatter_css: Bail on EOF-recovered parse errors (#24282) (leaysgur)
42ec8de formatter: Keep comments inside surviving parens and suppressed statement terminators (#24253) (leaysgur)
1343779 formatter: Keep comment inline for empty statements (#24249) (leaysgur)
b996579 formatter: Print ; before trailing comments part 2 (#24246) (leaysgur)
4f86e8c formatter: Print ; before trailing comments (#24244) (leaysgur)
01252e4 formatter: Add or remove parens for let declaration (#24215) (leaysgur)

⚡ Performance

eeb1913 formatter_core: Avoid per-call Vec work-stack in soft-line removal (#23775) (Marius Schulz)
a2f255b formatter: Use SmallVec for MemberChain collections (#23776) (Marius Schulz)

📚 Documentation

b52d0f5 formatter: Add TODO comment about unsound code (#24372) (overlookmotel)

Co-authored-by: Boshen [email protected]
Original source
All of your release notes in one feed

Join Releasebot and get updates from Eslint and hundreds of other software products.

Create account
Get updates with:
Jul 14, 2026
Date parsed from source:
Jul 14, 2026

First seen by Releasebot:
Jul 15, 2026
Oxc

oxfmt_v0.59.0: release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)

Oxc releases updates for Oxlint and Oxfmt with new linter and formatter capabilities, broader config discovery, stronger autofix support, and many bug fixes for ignore patterns, comments, parens, and type handling, plus performance improvements across rules and formatting.
Oxlint

🚀 Features

0433a83 linter/eslint/no-inner-declarations: Add namespaces option (#24044) (Boshen)

92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)

8c1d74b linter/import/no-duplicates: Add autofix logic (#24273) (Cole Ellison)

🐛 Bug Fixes

0b086de linter/jest/prefer-lowercase-title: False positive when lowercaseFirstCharacterOnly is false (#24414) (Connor Shea)

097cb95 linter: Allow vite-plus/test and `@effect as Vitest source (#24196) (Liang)

8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)

9ba30e5 linter/oxc/bad-replace-all-arg: Add note to enhance diagnostic (#24346) (camc314)

2ce5a33 linter: Resolve ignorePatterns relative to the config dir (#24339) (leaysgur)

ab90eed linter/eslint/no-loop-func: Do not error on catch variables (#24316) (Chris Opperwall)

b67f0a6 linter/eslint/no-unused-vars: Count default parameter updates as usage (#24323) (camc314)

d193f8e linter: Detect Junie agent env vars (#24277) (Jeevan Mohan Pawar)

2aecf60 linter/eslint/no-unreachable: Handle break in switch stmts correctly (#24260) (camc314)

⚡ Performance

7f80cac linter/vue/prop-name-casing: Precompile ignoreProps regex pattern (#24413) (connorshea)

6272051 linter/typescript/no-require-imports: Compile allow patterns once (#24417) (connorshea)

fb1edf1 linter: Compute comment fix span only for directive comments (#24419) (connorshea)

33805b9 linter/jsdoc/require-param: Compile checkTypesPattern regex once (#24420) (connorshea)

8de6fca linter/jest/valid-title: Compile disallowedWords regex once (#24412) (Connor Shea)

4a0d8dc linter/eslint/no-underscore-dangle: Avoid String clone per identifier (#24371) (Ian Macalinao)

f3ab04c linter/typescript/consistent-type-imports: Remove redundant Vec per violation (#24370) (Ian Macalinao)

4d2d78d linter/typescript/prefer-ts-expect-error: Avoid String clone per comment (#24369) (Ian Macalinao)

Oxfmt

🚀 Features

3a7fe74 formatter_css: Update oxc-css-parser to 0.0.7 (#24434) (leaysgur)

0173cd3 formatter_css: Format Less :extend and merge props (#24358) (leaysgur)

92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)

df250df formatter: Support quoteProps for TS enum and methods (#24309) (leaysgur)

a9a5cd6 formatter_core: Expose SourceText::as_str() (#24281) (leaysgur)

🐛 Bug Fixes

162bddf formatter: Add required parens for conditional type in type parameter constraint (#24450) (leaysgur)

2d22a91 formatter: Determine type cast target from span instead of lexical scan (#24447) (leaysgur)

25306e9 formatter: Do not add extra parens with type cast comment (#24444) (leaysgur)

bd6edfe formatter: Break arrow signature that exactly fills the line when cond body may hug (#24440) (leaysgur)

a99ef41 formatter: Keep quotes on method signature named new (#24432) (leaysgur)

fcc28df formatter_css: Keep glued-braket-value tight (#24352) (leaysgur)

8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)

b7c7e15 formatter: Add parens for import and private field in new callee chain (#24320) (leaysgur)

0c8f6e4 formatter: Update detect_code_removal for #24309 (#24314) (leaysgur)

a85aad0 formatter: Fix member-chain and non-null parens (#24312) (leaysgur)

1c29c73 formatter: Preserve TSNonNullExpression in chain expression (#24311) (leaysgur)

8933c0e formatter: Keep comment inside of empty switch block (#24308) (leaysgur)

ec26af2 formatter: Preserve blank lines between JSX attrs (#24290) (leaysgur)

70bd54d formatter: Keep arrow function body comment (#24287) (leaysgur)

415fe1e oxfmt: Error on ignorePatterns that cannot match files outside the config directory (#24286) (leaysgur)

eeabc4a formatter_css: Bail on EOF-recovered parse errors (#24282) (leaysgur)

42ec8de formatter: Keep comments inside surviving parens and suppressed statement terminators (#24253) (leaysgur)

1343779 formatter: Keep comment inline for empty statements (#24249) (leaysgur)

b996579 formatter: Print ; before trailing comments part 2 (#24246) (leaysgur)

4f86e8c formatter: Print ; before trailing comments (#24244) (leaysgur)

01252e4 formatter: Add or remove parens for let declaration (#24215) (leaysgur)

⚡ Performance

eeb1913 formatter_core: Avoid per-call Vec work-stack in soft-line removal (#23775) (Marius Schulz)

a2f255b formatter: Use SmallVec for MemberChain collections (#23776) (Marius Schulz)

📚 Documentation

b52d0f5 formatter: Add TODO comment about unsound code (#24372) (overlookmotel)

Co-authored-by: Boshen [email protected]

Original source
Jul 14, 2026
Date parsed from source:
Jul 14, 2026

First seen by Releasebot:
Jul 15, 2026
Oxc

oxc crates_v0.140.0

Oxc releases a broad update with smarter minification, stronger semantic and transformer handling, and React compiler codegen improvements. It also fixes several edge cases around enums, bindings, decorators, and ambient types while speeding up core compiler and parser paths.

🚀 Features

5b20828 minifier: Extract sequence expression from expressions (#22003) (Armano)

616bfa2 minifier: Remove unreachable code after terminating statements (#24441) (Dunqing)

ddab89a data_structures: Add likely and unlikely functions (#24368) (overlookmotel)

a3a39f9 react_compiler: Implement enableEmitHookGuards codegen (#24329) (Boshen)

b79eef7 minifier: Apply De Morgan's law to negated comparison chains in jump guards and loop tests (#24279) (Dunqing)

34ff7b4 minifier: Drop write-only property assignments to unused local bindings by default (#24112) (Dunqing)

1b829d8 semantic: Record const enums in EnumData (#24268) (Dunqing)

ba0944c semantic: Add Scoping::set_symbol_span (#24221) (camc314)

🐛 Bug Fixes

edf781d minifier: Keep reads of never-assigned uninitialized bindings (#24452) (Dunqing)

7d33363 minifier: Preserve guaranteed throws from class heritage evaluation (#24349) (Dunqing)

058a62f semantic: Track ambient contexts in SemanticBuilder (#24327) (camc314)

721eb0b transformer/decorator: Scope accessor class binding (#24330) (camc314)

1ebdce3 semantic: Allow reserved keywords in ambient declaration types (#24325) (camc314)

460176a track-memory-allocations: Exclude arena chunks from Sys allocs (#24292) (Dunqing)

af4922b transformer: Clear lowered namespace redeclarations (#24300) (camc314)

ffd2765 semantic: Mark declared computed MethodDefinitions as type references (#24296) (camc314)

f17514b isolated-declarations: Emit const readonly fields as types (#24288) (camc314)

40f769d minifier: Make proto write tracking execution-order independent (#24280) (Dunqing)

6371fed transformer: Remove stale enum member bindings (#24272) (camc314)

f05dfab transformer: Correct symbol flags for lowered namespaces (#24271) (Dunqing)

84eeb55 transformer: Correct symbol flags for lowered enums (#24269) (Dunqing)

c3057da transformer: Preserve generated class binding spans (#24220) (camc314)

8260096 transformer: Correct span for lowered namespace symbol (#24222) (camc314)

42d00d3 semantic: Mark declared class heritage as type references (#24237) (camc314)

588d997 semantic: Mark TS PropertyDefinitions computed fields as type references (#24233) (camc314)

9b95632 semantic: Mark computed method keys in TSMethodSignatures as type references (#24232) (camc314)

⚡ Performance

48911ec react_compiler: Use FxHashSet for membership-only block sets (#24486) (Boshen)

1e3e626 react_compiler: Reduce allocations in reactive-places and mutation-aliasing passes (#24476) (Boshen)

e86e0d8 react_compiler: Avoid copying the aliasing fixpoint's abstract state (#24117) (Marius Schulz)

5b26643 transformer_plugins: Dispatch global defines by trailing name (#23666) (Boshen)

dce0f29 react_compiler: Replace all compiled functions in a single AST walk (#24403) (Boshen)

f85f0d8 ast: Delegate inherited enum variants in clone_in and estree derives (#23555) (Boshen)

3ff0234 allocator: Remove unwrap from ReplaceWith (#24365) (overlookmotel)

ab22e80 transformer: Fix Rust 1.97 performance regression (#24354) (camc314)

b47585c parser: Use ReplaceWith instead of TakeIn (#24018) (overlookmotel)

b227a06 minifier: Use ReplaceWith instead of TakeIn (#24017) (overlookmotel)
Original source
Jul 14, 2026
Date parsed from source:
Jul 14, 2026

First seen by Releasebot:
Jul 15, 2026
Oxc

oxlint v1.74.0 & oxfmt v0.59.0

Oxc releases Oxlint v1.74.0 and Oxfmt v0.59.0 with new linting and formatting features, broader .mts config discovery, autofix improvements, many bug fixes, and performance gains across lint, formatter, and CSS handling.
Table of Contents

Oxlint v1.74.0

Oxfmt v0.59.0

Oxlint v1.74.0

Oxlint v1.74.0

🚀 Features

0433a83 linter/eslint/no-inner-declarations: Add namespaces option (#24044) (Boshen)
92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)
8c1d74b linter/import/no-duplicates: Add autofix logic (#24273) (Cole Ellison)

🐛 Bug Fixes

ac7176d linter/import/no-duplicates: Avoid duplicate commas when merging imports (#24467) (camc314)
261aa39 linter/import/no-duplicates: Preserve type modifiers when merging imports (#24466) (camc314)
dbd08b6 linter/unicorn/prefer-string-raw: Skip fix for TSPropertySignature keys (#24465) (camc314)
df67932 linter: Skip suppression validation with --type-check-only (#24462) (Stephen Zhou)
0b086de linter/jest/prefer-lowercase-title: False positive when lowercaseFirstCharacterOnly is false (#24414) (Connor Shea)
097cb95 linter: Allow vite-plus/test and `@effect as Vitest source (#24196) (Liang)
8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)
9ba30e5 linter/oxc/bad-replace-all-arg: Add note to enhance diagnostic (#24346) (camc314)
2ce5a33 linter: Resolve ignorePatterns relative to the config dir (#24339) (leaysgur)
ab90eed linter/eslint/no-loop-func: Do not error on catch variables (#24316) (Chris Opperwall)
b67f0a6 linter/eslint/no-unused-vars: Count default parameter updates as usage (#24323) (camc314)
d193f8e linter: Detect Junie agent env vars (#24277) (Jeevan Mohan Pawar)
2aecf60 linter/eslint/no-unreachable: Handle break in switch stmts correctly (#24260) (camc314)

⚡ Performance

2efa2f9 linter/react/jsx-handler-names: Simplify JSX handler name normalization (#24458) (camc314)
9c4e24a linter/eslint/object-shorthand: Remove constructor regex (#24457) (camc314)
7f80cac linter/vue/prop-name-casing: Precompile ignoreProps regex pattern (#24413) (connorshea)
6272051 linter/typescript/no-require-imports: Compile allow patterns once (#24417) (connorshea)
fb1edf1 linter: Compute comment fix span only for directive comments (#24419) (connorshea)
33805b9 linter/jsdoc/require-param: Compile checkTypesPattern regex once (#24420) (connorshea)
8de6fca linter/jest/valid-title: Compile disallowedWords regex once (#24412) (Connor Shea)
4a0d8dc linter/eslint/no-underscore-dangle: Avoid String clone per identifier (#24371) (Ian Macalinao)
f3ab04c linter/typescript/consistent-type-imports: Remove redundant Vec per violation (#24370) (Ian Macalinao)
4d2d78d linter/typescript/prefer-ts-expect-error: Avoid String clone per comment (#24369) (Ian Macalinao)

Oxfmt v0.59.0

🚀 Features

3a7fe74 formatter_css: Update oxc-css-parser to 0.0.7 (#24434) (leaysgur)
0173cd3 formatter_css: Format Less :extend and merge props (#24358) (leaysgur)
92f154a oxlint,oxfmt: Auto-discover .mts config files (#24357) (camc314)
df250df formatter: Support quoteProps for TS enum and methods (#24309) (leaysgur)
a9a5cd6 formatter_core: Expose SourceText::as_str() (#24281) (leaysgur)

🐛 Bug Fixes

95262b9 formatter_css: Keep more value comments before comma (#24487) (leaysgur)
cd53d98 formatter_css: Keep value comments before comma (#24484) (leaysgur)
27f57d8 formatter: Type alias comment idempotency (#24483) (leaysgur)
b7b82e0 formatter: Suppressed trailing semi (#24482) (leaysgur)
162bddf formatter: Add required parens for conditional type in type parameter constraint (#24450) (leaysgur)
2d22a91 formatter: Determine type cast target from span instead of lexical scan (#24447) (leaysgur)
25306e9 formatter: Do not add extra parens with type cast comment (#24444) (leaysgur)
bd6edfe formatter: Break arrow signature that exactly fills the line when cond body may hug (#24440) (leaysgur)
a99ef41 formatter: Keep quotes on method signature named new (#24432) (leaysgur)
fcc28df formatter_css: Keep glued-braket-value tight (#24352) (leaysgur)
8337835 linter: Error on ignorePatterns that cannot match files aoutside the config directory (#24341) (leaysgur)
b7c7e15 formatter: Add parens for import and private field in new callee chain (#24320) (leaysgur)
0c8f6e4 formatter: Update detect_code_removal for #24309 (#24314) (leaysgur)
a85aad0 formatter: Fix member-chain and non-null parens (#24312) (leaysgur)
1c29c73 formatter: Preserve TSNonNullExpression in chain expression (#24311) (leaysgur)
8933c0e formatter: Keep comment inside of empty switch block (#24308) (leaysgur)
ec26af2 formatter: Preserve blank lines between JSX attrs (#24290) (leaysgur)
70bd54d formatter: Keep arrow function body comment (#24287) (leaysgur)
415fe1e oxfmt: Error on ignorePatterns that cannot match files outside the config directory (#24286) (leaysgur)
eeabc4a formatter_css: Bail on EOF-recovered parse errors (#24282) (leaysgur)
42ec8de formatter: Keep comments inside surviving parens and suppressed statement terminators (#24253) (leaysgur)
1343779 formatter: Keep comment inline for empty statements (#24249) (leaysgur)
b996579 formatter: Print ; before trailing comments part 2 (#24246) (leaysgur)
4f86e8c formatter: Print ; before trailing comments (#24244) (leaysgur)
01252e4 formatter: Add or remove parens for let declaration (#24215) (leaysgur)

⚡ Performance

eeb1913 formatter_core: Avoid per-call Vec work-stack in soft-line removal (#23775) (Marius Schulz)
a2f255b formatter: Use SmallVec for MemberChain collections (#23776) (Marius Schulz)

📚 Documentation

3b7fb91 formatter_css: Update AGENTS.md and examples (#24488) (leaysgur)
b52d0f5 formatter: Add TODO comment about unsound code (#24372) (overlookmotel)
Original source
Jul 13, 2026
Date parsed from source:
Jul 13, 2026

First seen by Releasebot:
Jul 13, 2026
typescript-eslint

v8.64.0

typescript-eslint releases import defer parsing support and updates no-loop-func plus key fixes in the latest 8.64.0 release.

8.64.0 (2026-07-13)

🚀 Features

support parsing import defer (#12513)

eslint-plugin: [no-loop-func] support using / await using declarations and deprecate the rule (#12500)

typescript-estree: throw for invalid definite assignment in class properties (#12543)

🩹 Fixes

eslint-plugin: [require-array-sort-compare] handle constrained arrays (#12512)

❤️ Thank You

Evyatar Daud @StyleShit

송재욱

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.
Original source
Jul 10, 2026
Date parsed from source:
Jul 10, 2026

First seen by Releasebot:
Jul 10, 2026
Eslint

ESLint v9.39.5 released

Eslint ships v9.39.5 as a patch release that fixes bugs and prevents crashes in host environments where require.cache is unavailable, including Yarn Plug’n’Play. It also includes documentation and maintenance updates.
We just pushed ESLint v9.39.5, which is a patch release upgrade of ESLint. This release fixes several bugs found in the previous release.

Highlights

This release backports a fix originally released in v10.3.0 that prevents ESLint from crashing in host environments where require.cache is unavailable, such as Yarn Plug’n’Play.

Bug Fixes

253be16 fix: handle unavailable require cache (backport of #20812 to v9.x) (#21065) (Eric)

Documentation

74930ed docs: switch build to Node.js 24 (#20894) (Milos Djermanovic)

eaec8bb docs: Add ESLint v9.x EOL notice (#20828) (Milos Djermanovic)

Chores

458205f chore: update @eslint/eslintrc and @eslint/js for v9.39.5 (#21077) (Francesco Trotta)

202117b chore: package.json update for @eslint/js release (Jenkins)

d9eb6ed test: disable warning for vm.constants.USE_MAIN_CONTEXT_DEFAULT_LOADER (#21074) (Francesco Trotta)

7b431a7 chore: override re2 dependency for @metascraper/helpers (#21068) (Milos Djermanovic)

daf7791 chore: pin [email protected] (#20895) (Milos Djermanovic)

daee8ba ci: use pnpm in eslint-flat-config-utils type integration test (#20829) (Milos Djermanovic)

116d4be ci: unpin Node.js 25.x in CI (#20619) (Copilot)

Original source
Jul 10, 2026
Date parsed from source:
Jul 10, 2026

First seen by Releasebot:
Jul 10, 2026
Eslint

ESLint v10.7.0 released

Eslint ships v10.7.0 with new rule options, smarter suggestions, and bug fixes. The release adds constructor callback nesting checks, custom error class handling in preserve-caught-error, and improved no-compare-neg-zero guidance, while tightening several rules and docs.
We just pushed ESLint v10.7.0, which is a minor release upgrade of ESLint. This release adds some new features and fixes several bugs found in the previous release.

Highlights

New option checkConstructorCallCallbacks in max-nested-callbacks

The max-nested-callbacks rule now supports a checkConstructorCallCallbacks option. When enabled, the rule also counts callback functions passed to constructor calls with new, such as new Promise((resolve) => {}), when calculating nesting depth.

For example, with { "max": 1, "checkConstructorCallCallbacks": true }, the rule reports the following code as exceeding the allowed callback nesting depth:

run(() => { new Promise(resolve => resolve()); });

New option errorClassNames in preserve-caught-error

The preserve-caught-error rule now supports an errorClassNames option. This option lets you specify additional custom error class names that must preserve the original caught error by passing it as a cause.

For example, with { "errorClassNames": ["MyError"] }, the following code is reported because the thrown MyError does not include the original error as a cause, just like built-in error types must:

try { doSomething(); } catch (error) { throw new MyError("something went wrong"); }

Suggestions for no-compare-neg-zero

The no-compare-neg-zero rule now supports suggestions. Where appropriate, it suggests replacing -0 with 0 or using Object.is() instead of operators such as === or !==. For example, for an expression such as x === -0, the rule suggests x === 0 to preserve the existing comparison behavior, and Object.is(x, -0) to distinguish -0 from +0.

Features

cf2a9bf feat: add errorClassNames option to preserve-caught-error rule (#21032) (sethamus)

f8b873a feat: max-nested-callbacks option for constructor callbacks (#21063) (fnx)

557fde8 feat: support computed Number.parseInt member access in radix rule (#21041) (Pixel)

0b4a73b feat: add suggestions to no-compare-neg-zero (#21034) (den$)

96cdd42 feat: report invalid signed numeric values in radix rule (#21030) (Pixel)

Bug Fixes

3e7bf15 fix: apply ignoreClassesWithImplements to class expressions (#21069) (Pixel)

0d7d70c fix: insert cause outside wrapping parens in preserve-caught-error (#21062) (Mahin Anowar)

75ec753 fix: handle static template literals in eqeqeq rule (#21058) (Pixel)

b717a22 fix: prevent eqeqeq null option from reporting non-equality operators (#21057) (Pixel)

e35b05f fix: avoid no-invalid-regexp false positive for shadowed RegExp (#21051) (Pixel)

a3172b6 fix: avoid no-control-regex false positive for shadowed RegExp (#21050) (Pixel)

d1f637e fix: parenthesize sequence expression operands in no-implicit-coercion (#21045) (spokodev)

8859baf fix: avoid prefer-numeric-literals false positive for shadowed globals (#21047) (한국)

a9e5961 fix: use-isnan false positive on shadowed NaN/Number (#20958) (sethamus)

8a240a7 fix: avoid false positives in radix rule for spread arguments (#21044) (Pixel)

Documentation

c30d808 docs: Update README (GitHub Actions Bot)

5139800 docs: document ESLint migration codemods in v9 and v10 guides (#20980) (Alex Bit)

04174cb docs: Update README (GitHub Actions Bot)

026e130 docs: update semver policy for bug fixes (#21048) (Milos Djermanovic)

9d42fef docs: Update README (GitHub Actions Bot)

b230159 docs: Update README (GitHub Actions Bot)

0129972 docs: correct **/.js glob to **/*.js in config files guide (#21036) (EduardF1)

Chores

9489379 chore: update dependency @eslint/eslintrc to ^3.3.6 (#21076) (renovate[bot])

81a4774 chore: updates for v9.39.5 release (Jenkins)

9835414 chore: enable $ExpectType annotations in all TypeScript files (#21071) (Francesco Trotta)

72adf6b chore: restrict markdownlint-cli2 updates in renovate (#21067) (lumir)

833ec10 chore: update dependency prettier to v3.9.4 (#21061) (renovate[bot])

7ea106d chore: update ecosystem plugins (#21059) (ESLint Bot)

8fb550e chore: add prettier update commit to .git-blame-ignore-revs (#21056) (lumir)

e4e1166 chore: update dependency prettier to v3.9.1 (#21055) (renovate[bot])

0493f53 chore: update prettier to v3.9.0 (#21054) (Pixel)

1056a99 chore: update dependency prettier to v3.8.5 (#21049) (renovate[bot])

4d4155d ci: run ecosystem tests on pull requests (#21027) (sethamus)

993539f chore: update dependency @eslint/json to ^2.0.1 (#21042) (renovate[bot])

53f8b69 test: add error locations to no-constant-binary-expression (#21039) (lumir)

5ab71d5 refactor: clean up radix rule internals (#21015) (Pixel)

a80a9a4 chore: update ecosystem plugins (#21035) (ESLint Bot)

7c9a029 ci: add Node.js 26 to CI (#20847) (lumir)

Original source
Jul 8, 2026
Date parsed from source:
Jul 8, 2026

First seen by Releasebot:
Jul 8, 2026
TypeScript by Microsoft

Announcing TypeScript 7.0

TypeScript ships its native TypeScript 7 port, bringing major speedups, lower memory use, rebuilt watch mode, parallel builds, and updated editor support for a faster, more stable development experience.
Today we are proud to announce the availability of TypeScript 7, a 10x faster native port of TypeScript!

Since its early days, TypeScript has promised to deliver on JavaScript that scales. By bringing strong type-checking and rich tooling to the world of JavaScript, TypeScript made it possible to build non-trivial high-quality apps across platforms.

Last year, our team unveiled TypeScript’s next step in scaling: making every part of the toolset an order of magnitude faster. The mission was a native port of TypeScript built in Go that could make the most of modern hardware. This port was done as faithfully as possible, writing new code while maintaining the structure and logic of the original codebase to keep results consistent and compatible between the two compilers. The key difference is that with this new codebase, TypeScript 7 brings native code speed, shared memory multithreading, and a number of new optimizations that typically yield speedups between 8x and 12x on full builds.

Just as with any other release, TypeScript 7 is available via npm:

npm install -D typescript

That will get you the new tsc executable in your workspace (which you can run via npx tsc). Of course, a big part of the TypeScript experience is also about editor support. Your favorite code editor should easily support TypeScript 7 with its new support for the language server protocol (LSP), and its new speed and multithreading improvements. Whether you’re using something like VS Code, Visual Studio, WebStorm, or any other modern editor, TypeScript 7 should work great. Just check your editor’s documentation – for example, VS Code has a dedicated extension for TypeScript 7 that you can use today, and Visual Studio will automatically enable TypeScript 7 based on your workspace.

What Does A Faster TypeScript Mean?

A faster TypeScript sounds great on paper, but what does it mean in practice? Maybe it helps to think about where TypeScript comes up at every stage of development.

A typical day of development might involve opening your editor, opening a TypeScript file, and running an operation like find-all-references across your projects. Then as you’d start to make edits, maybe you’d expect auto-completions to pop up, and get red squiggles on the fly as you’d make edits. When you (and more recently, perhaps an AI agent) were ready to build your project, you’d run tsc, check the output for errors, and then run your generated code somehow.

A faster TypeScript means every part above is streamlined. Waiting for your editor to fully load your project will feel instantaneous. Delays on find-all-references, auto-completion, and diagnostics should take a fraction of the time they used to. And when you run tsc, maybe in --watch mode, you’ll be able to tighten your feedback loop and iterate faster than ever before.

You can see this on real-world projects. In fact, you can try comparing on a few open-source projects yourself. Here are the build times of running TypeScript 6 and 7 on some fairly large open source codebases.

Codebase | TypeScript 6 | TypeScript 7 | Speedup
vscode | 125.7s | 10.6s | 11.9x
sentry | 139.8s | 15.7s | 8.9x
bluesky | 24.3s | 2.8s | 8.7x
playwright | 12.8s | 1.47s | 8.7x
tldraw | 11.2s | 1.46s | 7.7x

TypeScript 7 also typically does better while asking for less aggregate memory over the span of a build.

Codebase | TypeScript 6 | TypeScript 7 | Memory Delta
vscode | 5.2GB | 4.2GB | -18%
sentry | 4.9GB | 4.6GB | -6%
bluesky | 1.8GB | 1.3GB | -26%
playwright | 1.0GB | 0.9GB | -11%
tldraw | 0.6GB | 0.5GB | -15%

Of course, there’s more to the experience than the full build. On the same computer, opening a file with an error in the VS Code codebase would previously take about 17.5 seconds from the time you opened the editor to the time you saw the first error. With TypeScript 7, it’s under 1.3 seconds – over 13x faster.

Battle-Tested and Ready for Production

The TypeScript project contains tens of thousands of tests built over more than a decade that run on every commit on our main branch. They’ve ensured every one of our releases is stable and reliable.

But TypeScript 7 is no ordinary release. Beyond our test suite, we’ve leveraged a number of different resources to make sure TypeScript 7 is solid for production use.

Over the last year we’ve worked with many large teams internally and externally to test TypeScript 7 on real-world codebases. The results have been overwhelmingly positive, with entire companies reporting that TypeScript 7 has been stable, fast, and easy to adopt. For example, the VS Code team recently highlighted their experience with TypeScript 7’s preview releases to move faster in their development cycle. We’ve also worked with Microsoft teams like Loop, Office, PowerBI, Teams, and Xbox to ensure that TypeScript is ready for the largest of codebases. Likewise, companies like Bloomberg, Canva, Figma, Google, Lattice, Linear, Miro, Notion, Sentry, Slack, Vanta, Vercel, VoidZero, and more have worked with us to test TypeScript 7 on their codebases and given us feedback to make it better.

Additionally, we’ve rebuilt much of our broader test infrastructure to run on TypeScript 7. TypeScript 6 and earlier had automated and on-demand testing for TypeScript and JavaScript projects on GitHub to detect regressions in the compiler and language service. The same testing is back, and running against TypeScript 7, finding issues in real codebases so we can find gaps in our core test suite and ship a better experience.

The combination of explicit feedback, automated crash reports, and aggressive testing has made a measurable difference in quality. In fact, our data insights have shown us that TypeScript 7.0’s new language server has actually reduced failing language server commands by over 80%, and reduced server crashes by over 60% compared to that of TypeScript 6.0.

We’ve also heard some incredible feedback from teams at scale:

Slack engineers have told us that TypeScript 7 eliminated 40% of their merge queue time and brought type-checking time in CI from about 7.5 minutes to 1.25 minutes. Local development in the editor was previously almost “unusable” due to language server load times and engineers would typically let CI do a full type-check. TypeScript 7 has been able to load the same codebase in a few seconds and made local type-checking feasible again.

Builds at Vanta have dramatically improved, showing a speedup of up to 9x faster on one of their biggest projects.

Similarly, the News Services team at Microsoft told us that adopting TypeScript 7 saved them 400 hours a month waiting for CI builds.

Last year, engineers working on PowerBI described TypeScript 7 in the editor as “life-saving” for working on their codebase. They adopted the experience as a default even before TypeScript 7 supported rename functionality in VS Code.

Developers working on Loop’s monorepo were also ecstatic. The previous editor experience was described as unusable at their scale, whereas the TypeScript 7 experience has been “amazing” to use.

Canva developers have told us that TypeScript 7’s language service shows dramatic speedups, going from about 58 seconds to seeing the first error in their editors to about 4.8 seconds.

Running Side-by-Side with TypeScript 6.0

While TypeScript 7.0 is here, it does not ship with an API. We expect TypeScript 7.1 to ship with a new (and different) API, but until then we have made it a priority to ensure TypeScript can be run side-by-side with TypeScript 6.0 for utilities that still need some programmatic access to the compiler (such as typescript-eslint).

As part of the 6.0/7.0 transition process, we’ve published a new compatibility package, @typescript/typescript6. This package provides an executable named tsc6, so that if needed, you can install TypeScript 7.0 (which ships its own tsc binary) side-by-side without naming conflicts. The new package also re-exports the TypeScript 6.0 API, so that you can use tsc for TypeScript 7, while other tooling can continue to rely on 6.0.

Because some tools like typescript-eslint expect to import from typescript directly via peer dependencies, we recommend achieving this via npm aliases. You should be able to run the following command

npm install -D typescript@npm:@typescript/typescript6

or modify your package.json as follows:

{ "devDependencies": { "typescript": "npm:@typescript/typescript6@^6.0.2" } }

Note that doing this will leave you only with a tsc6 executable. To get 7.0’s tsc, you can add another alias for TypeScript 7 and npx tsc will just work with 7.0:

{ "devDependencies": { "@typescript/native": "npm:typescript@^7.0.2", "typescript": "npm:@typescript/typescript6@^6.0.2" } }

Nightly Builds and @typescript/native-preview

Until now, most developers have installed TypeScript 7 via the @typescript/native-preview package. This package shipped nightly builds of the new codebase, and has served the community well with over 8.5 million weekly downloads!

However, going forward, nightly builds will soon resume under the standard typescript package with the next tag. You can install it with:

npm install -D typescript@next

Custom Scaling: Parallelization and Controls

TypeScript 7.0 now performs many steps in parallel, including parsing, type-checking, and emitting. Some of these steps, like parsing and emitting can mostly be done independently across files. As such, parallelization automatically scales well with larger codebases with relatively little overhead. But not every step in a TypeScript build is easily parallelizable.

TypeScript 7 introduces the experimental --checkers and --builders flags to fine-tune the parallelization behavior for less-trivial steps like type-checking and project reference building. It also introduces a --singleThreaded flag to disable parallelization entirely, which can be useful for debugging or running in environments with limited resources.

Type-Checker Parallelization

Other steps, like type-checking, have more complex dependencies across files. Most files end up relying on the same type information from their dependencies and the global scope, and so running type-checkers completely independently would be wasteful – both in computation and memory. On the other hand, type-checking occasionally relies on the relative ordering of information in a program, and so type-checking from scratch must always check the same files in an identical order to ensure the same results.

To enable parallelization while avoiding these pitfalls, TypeScript 7.0 creates a fixed number of type-checker workers with their own view of the world. These type-checking workers may end up duplicating some common work, but given the same input files, they will always divide them identically and produce the same results.

The default number of type-checking workers is 4, but it can be configured with the new --checkers flag. You may find that increasing this number can further speed up builds on larger codebases where typical machines have more CPU cores, but will typically come at the cost of increased memory usage. For example, in the table above, we ran TypeScript 7 with its default of --checkers 4. Here’s what the results look like on the same machine with --checkers 8.

Codebase | TypeScript 6 | TypeScript 7 (--checkers 8) | Speedup
vscode | 125.7s | 7.51s | 16.7x
sentry | 139.8s | 12.08s | 11.6x
bluesky | 24.3s | 2.01s | 12.1x
playwright | 12.8s | 1.16s | 11x
tldraw | 11.2s | 1.06s | 10.6x

As you can see, these codebases get a better speedup from dedicating more cores, but results will differ across projects and underlying machines.

On the other hand, on machines with fewer CPU cores and less memory (e.g. CI runners) you may want to decrease this number to avoid unnecessary or incidental overhead. You can specify a value as low as --checkers 1, effectively making type-checking single-threaded and eliminating duplicate work.

In rare cases, varying the number of --checkers may surface order-dependent results. Specifying a fixed number of checkers across build environments can help ensure everyone is getting the same results, but is up to the discretion of your team.

Project Reference Builder Parallelization

TypeScript 7.0 can parallelize builds within a project, but it can now also build multiple projects at once as well. This behavior can be configured with the new --builders flag, which controls the number of parallel project reference builders that can run at once when running under --build. This can be particularly helpful for monorepos with many projects.

Like --checkers, increasing the number of builders can speed up builds, but may come at the cost of increased memory usage. It also has a multiplicative effect with --checkers, so it’s important to find the right balance for your machine and codebase. For example, building with --checkers 4 --builders 4 allows up to 16 type-checkers to run at once, which may be excessive.

Unlike --checkers, varying the number of builders should not produce different results; however, building project references is fundamentally bottlenecked by the dependency graph of projects (with the exception of type-checking on codebases that leverage --isolatedDeclarations and separate syntactic declaration file emit).

Single-Threaded Mode

In some cases, it can be helpful to enforce single-threaded operation throughout the compiler. This may be useful for debugging, comparing performance with TypeScript 6 and 7, when orchestrating parallel builds externally, or for running in environments with very limited resources. To enable single-threaded mode, you can use the new --singleThreaded flag. This will not only cap the number of type-checking workers to 1, but also ensure parsing and emitting are done in a single thread.

Improved --watch Mode

TypeScript 7 ships with a completely rebuilt --watch mode.

--watch is now powered by a new foundation based on the Parcel bundler’s file-watcher that provides efficient and stable cross-platform file watching capabilities.

When our team set out to port our file watching logic, we encountered a few challenges with cross-platform file watching in Go. The standard library doesn’t provide a built-in file watching API, and existing third-party libraries we explored had various issues with stability, performance, cross-platform support, or issues with build tooling integration. We were able to build solutions around polling periodically to check for file changes, and this worked broadly across operating systems; however it was computationally expensive, especially at larger-scale projects with many dependencies in node_modules. Even with dynamic scheduling strategies, we found that pure-polling solutions were too taxing for general use.

For many years, Visual Studio Code has relied on @parcel/watcher, and in recent years TypeScript in VS Code has relied on its file watching capabilities indirectly. While it seemed promising, one of the problems for us with Parcel’s watcher is that it’s written in C++, and in turn requires a full C++ toolchain to build. Given our positive experience with Parcel’s watcher in VS Code, we explored porting it to Go with a few minimal assembly shims to avoid introducing a new toolchain dependency.

The exploration has been a success – what started as a very direct translation from C++ to Go was further refined into idiomatic Go that still passes the ported test suite. The watcher is a self-contained package that has allowed us to keep a clean separation of concerns between what we care to watch and why. We are now seeing significant resource improvements in --watch mode across platforms, and have been hearing positive feedback from earlier users of TypeScript 7.

We’d like to extend our thanks to Devon Govett whose work on Parcel has provided immense benefits to both the Visual Studio Code and TypeScript projects. We hope this port will provide opportunities and insights for the original Parcel watcher codebase over time.

Updates Since 5.x, and New Behaviors from 6.0

TypeScript 7.0 is made to be compatible with TypeScript 6.0’s type-checking and command-line behavior. Practically any TypeScript code that compiles cleanly with TypeScript 6.0 (with the stableTypeOrdering flag on, and without any ignoreDeprecations flag set) should compile identically in TypeScript 7.0.

With that said, TypeScript 7.0 adopts 6.0’s new defaults, and provides hard errors in the face of any flags and constructs deprecated in TypeScript 6.0. This is notable as 6.0 is still relatively new, and many projects will need to adapt to its new behaviors. We encourage developers to adopt TypeScript 6.0 to make the transition to TypeScript 7.0 easier, and you can also read the TypeScript 6.0 release blog post for more details on these deprecations.

At a glance, the notable default changes to configuration are:

strict is true by default.

module defaults to esnext.

target defaults to the current stable ECMAScript version immediately preceding esnext.

noUncheckedSideEffectImports is true by default.

libReplacement is false by default.

stableTypeOrdering is true by default, and cannot be turned off.

rootDir now defaults to ./, and inner source directories must be explicitly set.

types now defaults to [], and the old behavior can be restored by setting it to ["*"] .

We believe the rootDir and types changes may be the most “surprising” changes, but they can be mitigated easily. Projects where the tsconfig.json sits outside of a directory like src will simply need to include rootDir to preserve the same directory structure.

For the types change, projects that depend on specific global declarations will need to list them explicitly. For example,

The deprecations that have turned into hard errors with no-op behavior are:

target: es5 is no longer supported.

downlevelIteration is no longer supported.

moduleResolution: node/node10 are no longer supported, with nodenext and bundler being recommended instead.

module: amd, umd, systemjs, none are no longer supported, with esnext or preserve being recommended in conjunction with bundlers or browser-based module resolution.

baseUrl is no longer supported, and paths can be updated to be relative to the project root instead of baseUrl.

moduleResolution: classic is no longer supported, and bundler or nodenext are the recommended replacements.

esModuleInterop and allowSyntheticDefaultImports cannot be set to false.

alwaysStrict is assumed to be true and can no longer be set to false.

The module keyword cannot be used in namespace declarations.

The asserts keyword cannot be used on imports, and must use the with keyword instead (to align with developments on ECMAScript’s import attribute syntax).

/// directives are no longer respected under skipDefaultLibCheck.

Command line builds cannot take file paths when the current directory contains a tsconfig.json file unless passed an explicit --ignoreConfig flag.

Template Literal Types Now Preserve Unicode Code Points

TypeScript 7.0 now treats Unicode code points more naturally when inferring from template literal types. For example:

Previously, TypeScript followed JavaScript’s UTF-16 indexing behavior here and split "😀" into two halves of a surrogate pair (\ud83d and \ude00). That was technically consistent with indexing in JavaScript (e.g. the inferred Head type was equal to "😀abc"[0]), but it usually wasn’t what people intended, and could produce string literal types containing unpaired surrogates that aren’t semantically meaningful.

This is a breaking change for type-level string manipulation that intentionally modeled UTF-16 code units, such as some string Length utilities. In practice, we expect the new behavior to be more useful and less surprising: template literal inference now follows the same intuition as iterating a string with for...of or spreading it with [...str], where "😀" is treated as one unit.

JavaScript Differences

As we ported the existing codebase, we also took the opportunity to revisit how our JavaScript support works.

TypeScript originally supported JavaScript files by using JSDoc comments and recognizing certain code patterns for analysis and type inference. Lots of the time, this was based on popular coding patterns, but occasionally it was based on whatever people might be writing that Closure and the JSDoc doc generating tool might understand. While this approach was helpful for developers with loosely-written JSDoc codebases, it required a number of compromises and special cases to work well, and diverged in a number of ways from TypeScript’s analysis in .ts files.

In TypeScript 7.0, we have reworked our JavaScript support to be more consistent with how we analyze TypeScript files. Some of the differences include:

Values cannot be used where types are expected – instead, write typeof someValue

@enum is not specially recognized anymore – create a @typedef on (typeof YourEnumDeclaration)[keyof typeof YourEnumDeclaration].

A standalone ? is no longer usable as a type – use any instead.

@class does not make a function a constructor – use a class declaration instead.

Postfix ! is not supported – just use T.

Type names must be defined within a @typedef tag (i.e. /** @typedef {T} TypeAliasName /), not adjacent to an identifier (i.e. /* @typedef {T} */ TypeAliasName;).

Closure-style function syntax (e.g. function(string): void) is no longer supported – use TypeScript shorthands instead (e.g. (s: string) => void).

Additionally, some JavaScript patterns, like aliasing this and reassigning the entirety of a function’s prototype are no longer specially treated.

While some of our JS support is in flux, we have been updating this CHANGES.md file to capture the differences between TypeScript 6.0 and 7.0 in more detail.

Editor Experience

As we mentioned above, TypeScript 7.0’s performance improvements are not limited to the command line experience – they also extend to the editor experience too. For VS Code users, we have a dedicated extension for TypeScript 7. When you install this extension, it will automatically become the default experience. You can disable and re-enable it at any time with the “Disable TypeScript 7 Language Server” and “Enable TypeScript 7 Language Server” commands from the command palette. In the coming weeks support for TypeScript 7 will ship as part of VS Code itself.

For Visual Studio users, the latest version of the IDE will automatically enable TypeScript 7 based on your workspace. You won’t need to do anything differently.

Of course, TypeScript 7 should work great in any editor of your choosing. The new foundation is built on the Language Server Protocol (LSP) and is able to leverage multiple threads to serve simultaneous requests as quickly as possible.

Since it first debuted, we’ve added in missing functionality like auto-imports, expandable hovers, inlay hints, code lenses, go-to-source-definition, JSX linked editing and tag completions, and more. Missing features from TypeScript 7.0 beta, such as semantic highlighting, “sort imports”, “remove unused imports”, and more are now in.

Additionally, we’ve continued to drive performance and stability in the past few months. We’ve rebuilt much of our testing and diagnostics infrastructure to make sure the quality bar is high, in which we are able to fuzz-test the language server against the top TypeScript and JavaScript codebases on GitHub. As we’ve mentioned above, TypeScript 7’s new language server is significantly more stable than TypeScript 6’s.

TypeScript and Embedded Languages

It’s worth calling out that workflows that use Vue, MDX, Astro, Svelte, and others will likely not yet be able to leverage TypeScript 7. Similarly, specialized type-checking within templates like Angular will also likely not use TypeScript 7. This is mainly because TypeScript 7 does not yet expose a stable programmatic API, and so tools (such as Volar) which embed TypeScript into their own compilers and language services can only currently rely on TypeScript 6.0. We expect this to be a point-in-time issue, as we are committed to providing a solution here. We will be actively working with the maintainers of these projects to ensure TypeScript 7 supports these workflows.

Until then, we recommend that teams use TypeScript 7 in scenarios where language server plugins are not required. Projects using Angular can use a combination of TypeScript 7 to get fast project-wide error detection at the CLI with tsc, and TypeScript 6.0 for editor support. Projects using Vue, MDX, Astro, Svelte, and others will need to continue using TypeScript 6.0 for now. In VS Code, users can simply run the “Disable TypeScript 7 Language Server” command to revert to TypeScript 6.0.

The Road Forward

TypeScript 7.0 is a major milestone in the TypeScript project. This port has been the primary focus of our team for over a year, and with 7.0 out, we will be returning to new feature work, ergonomic improvements, more performance wins, and implementing a new API for the broader ecosystem. While that seems major, we expect a fairly similar timeline to releases prior to TypeScript 7.0, with new featureful versions published every 3-4 months. With TypeScript 7.1 on the horizon, we hope to bridge any gaps to help bring the community forward.

We also encourage you to share your experience using TypeScript 7.0 online. Feel free to follow and tag @typescriptlang.org on Bluesky or @[email protected] on Mastodon, or @typescript on Twitter, and let us and others know what you think of TypeScript 7.

We know this new release will be incredibly valuable for the TypeScript ecosystem. We hope that it makes your day-to-day coding experience more fast, fun, productive, and joyful.

Welcome to the native era of the TypeScript toolset.

Happy Hacking!

– The TypeScript Team
Original source
Jul 6, 2026
Date parsed from source:
Jul 6, 2026

First seen by Releasebot:
Jul 6, 2026
Oxc

oxlint_v1.73.0: release(apps): oxlint v1.73.0 && oxfmt v0.58.0 (#24219)

Oxc releases Oxlint and Oxfmt updates with new lint rules, broader rule options, faster type-aware linting, and many bug fixes. Oxfmt also adds formatter core improvements and CSS, GraphQL, and JSON formatting refinements, plus performance gains across the toolchain.

Oxlint

🚀 Features

7db7a29 allocator: Add ReplaceWith trait (#24012) (overlookmotel)

a2c97f3 linter/unicorn: Implement explicit-timer-delay rule (#23612) (Mikhail Baev)

85735cb linter/unicorn: Implement no-confusing-array-with rule (#23638) (Shekhu☺️)

cb4fbb9 linter/eslint: Implement no-unreachable-loop rule (#23975) (Todor Andonov)

dc32112 linter/eslint/no-constant-binary-expression: Check relational comparisons (#24088) (camc314)

439c344 linter/jsdoc: Added missing options to jsdoc/require-param rule (#23364) (kapobajza)

62af717 linter/unicorn/filename-case: Add lowercase and screamingSnakeCase (#24045) (Boshen)

d963967 linter/unicorn/no-array-sort: Add allowAfterSpread option (#24043) (Boshen)

0a75682 linter: Add per-rule timings for type-aware linting (#22488) (camchenry)

743e222 linter/react: Add disallowedValues option for forbid-dom-props rule (#23970) (Mikhail Baev)

🐛 Bug Fixes

7b80010 linter: Use direct binding symbol ids (#24216) (camc314)

8f94b49 linter/import/no-duplicates: Don't flag a type-only import beside a side-effect import (#24030) (Boshen)

d8c3fee linter/react/rules-of-hooks: Flag useEffectEvent escapes (#23764) (Rayan Salhab)

0a7312b linter/no-deprecated-functions: Map require.requireActual to jest.requireActual (#23627) (Jerry Zhao)

d9e3ab3 linter/eslint/no-useless-return: Handle switch case continuation (#23984) (camc314)

0b25582 ast: Type binding node typeAnnotation as TSTypeAnnotation | null (#23113) (Boshen)

122d112 linter/eslint/no-restricted-imports: Flag dynamic import() expressions (#24029) (Boshen)

59b6b83 linter: Avoid OnceLock re-entry on cyclic export * re-exports (#23632) (Jerry Zhao)

dd09af0 linter/import/namespace: Avoid panic on destructuring of an unresolvable namespace re-export (#23626) (Jerry Zhao)

bdb51c7 linter/jest/prefer-ending-with-an-expect: Validate config patterns (#24122) (camc314)

e383843 linter/unicorn/prefer-modern-dom-apis: Skip fixer for non identifier arguments (#23630) (Jerry Zhao)

0ac4c83 linter: Detect circular config extends (#24115) (camc314)

bae1edf linter/import/namespace: Check namespace imports after named imports (#24094) (camc314)

cd8fdfe linter/eslint/no-eval: Recognize Array.from family thisArg (#24091) (camc314)

851ee43 linter/eslint/no-eval: Resolve this binding for functions returned from an IIFE (#23643) (Jerry Zhao)

002ab35 linter/unicorn: Avoid prefer-array-find rest destructuring false positive (#23654) (ColemanDunn)

01c8775 linter/unicorn/filename-case: Keep digits attached in screamingSnakeCase (#24056) (Boshen)

f256941 linter: Recognize @effect/vitest as a vitest import source (#24025) (Boshen)

73eeb1d linter/import/extensions: Honor per-extension never for explicit extensions (#24031) (Boshen)

d4ebe1f linter: Reject non-object oxlint config files (#24026) (Boshen)

45d607d linter/react/forbid-component-props: Make allow/disallow lists optional in schema (#24024) (Boshen)

54076ad linter/unicorn/no-array-for-each: Suggest entries loop for index callbacks (#24004) (camc314)

d057736 linter/jsdoc: Avoid param root underflow (#23945) (camc314)

29c76bf linter/unicorn/prefer-at: Skip object numeric-key access (#23909) (Gaurav Dubey)

⚡ Performance

657a8fc linter/oxc/bad-array-method-on-arguments: Only run on member expressions instead of all identifiers (#24164) (camchenry)

073d9e7 linter/eslint/prefer-rest-params: Run on functions instead of all identifiers (#24163) (camchenry)

e5a4162 linter/jest/no-confusing-set-timeout: Early exit fast path (#24092) (camc314)

bca7ce5 linter: Only run react-perf rules on JSX attribute nodes (#24083) (camchenry)

6881bf6 linter: Compute apply_overrides rule set lazily (#23648) (Jerry Zhao)

911c106 linter/eslint/no-obj-calls: Use resolved reference instead of scope walk (#23895) (Marius Schulz)

dc8fd9a linter/unicorn/prefer-dom-node-text-content: Change dispatch to run only on less common node types (#23897) (Connor Shea)

fdbd34d linter/eslint/no-useless-call: Fast-path static callees (#24077) (camc314)

b1be114 linter/import/extensions: Skip empty config and borrow extensions (#24075) (camc314)

4781b2d linter/eslint/no-obj-calls: Use direct global matches (#24076) (camc314)

e6cee89 linter: Avoid node-chain allocation for non-Jest calls (#23907) (Yagiz Nizipli)

30dc517 linter/typescript/no-restricted-types: O(1) banned-type lookups (#23827) (Yagiz Nizipli)

📚 Documentation

6ca9125 linter/typescript: Clarify consistent-type-imports behavior (#23972) (camc314)

Oxfmt

🚀 Features

4f4313e formatter_css: Update oxc-css-parser 0.0.5 (#24120) (leaysgur)

0ccd8a1 formatter_graphql: Update oxc-graphql-parser 0.0.5 (#24106) (leaysgur)

89ec3d9 formatter_core: Add literal line and root indention primitives (#24051) (leaysgur)

213a96b formatter_core: Add no-expand-parent for multiline text (#24050) (leaysgur)

0e5bcc9 formatter_graphql: Update oxc-graphql-parser 0.0.4 (#24039) (leaysgur)

e0b35a1 formatter_css: Update [email protected] (#23974) (leaysgur)

🐛 Bug Fixes

1fe6546 formatter: Omit unneeded ; for type members with no-semi (#24212) (leaysgur)

0ad7316 formatter: Print space for ForStatement.update only if exists (#24211) (leaysgur)

3abbed5 formatter: Print ; before jsdoc type-cast parens with no-semi (#24208) (leaysgur)

9af3833 formatter_css: Make scss formatter consistent (#24207) (leaysgur)

46d7194 formatter_css: Use fill IR for @forward members (#24206) (leaysgur)

e31038f formatter_css: Keep comment inside sass config list (#24205) (leaysgur)

d3b9591 formatter: Add parens around await/yield with <T> (#24202) (leaysgur)

2121a55 oxfmt: Reuse tinypool process during the same LSP process (#24197) (leaysgur)

9bf4b4a formatter_css: Align CSS output to Prettier 3.9.1 (#24100) (leaysgur)

cd2452e formatter_css: Align SCSS output to Prettier 3.9.1 (#24097) (leaysgur)

4ee8745 formatter_css: Keep selector value contain line-break without breaking line (#24055) (leaysgur)

e1ece97 formatter_graphql: Break implements list by print-width (#23997) (leaysgur)

0a6b16c formatter_json: Preserve key and literal value for json-stringify (#23996) (leaysgur)

903ab6e formatter_css: Preserve newlines in css-in-js selector list (#23992) (leaysgur)

ea5d095 oxfmt: Update --migrate prettier (#23963) (leaysgur)

⚡ Performance

468e1e3 formatter_core: Make printer queues cursor-based (#24098) (Boshen)

c59f2fe rust: Return impl ExactSizeIterator from slice-backed accessors (#24144) (Boshen)

c292fb2 formatter: Inline fits element dispatcher (#23982) (camc314)

Co-authored-by: Boshen [email protected]
Original source

Linting and Formatting Release Notes

Products (5)

Latest Linting and Formatting Updates

Automating ESLint migrations with Codemod

What is Codemod?

ESLint v8 to v9 migration

Migrating configuration with @eslint/v8-to-v9-config

Migrating custom rules with @eslint/v8-to-v9-custom-rules

ESLint v9 to v10 migration

Conclusion

oxlint_v1.74.0: release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)

Oxlint

🚀 Features

🐛 Bug Fixes

⚡ Performance

Oxfmt

🚀 Features

🐛 Bug Fixes

⚡ Performance

📚 Documentation

oxfmt_v0.59.0: release(apps): oxlint v1.74.0 && oxfmt v0.59.0 (#24454)

Oxlint

🚀 Features

🐛 Bug Fixes

⚡ Performance

Oxfmt

🚀 Features

🐛 Bug Fixes

⚡ Performance

📚 Documentation

oxc crates_v0.140.0

🚀 Features

🐛 Bug Fixes

⚡ Performance

oxlint v1.74.0 & oxfmt v0.59.0

Table of Contents

Oxlint v1.74.0

🚀 Features

🐛 Bug Fixes

⚡ Performance

Oxfmt v0.59.0

🚀 Features

🐛 Bug Fixes

⚡ Performance

📚 Documentation

v8.64.0

8.64.0 (2026-07-13)

🚀 Features

🩹 Fixes

❤️ Thank You

ESLint v9.39.5 released

Highlights

Bug Fixes

Documentation

Chores

ESLint v10.7.0 released

Highlights

New option checkConstructorCallCallbacks in max-nested-callbacks

New option errorClassNames in preserve-caught-error

Suggestions for no-compare-neg-zero

Features

Bug Fixes

Documentation

Chores

Announcing TypeScript 7.0

What Does A Faster TypeScript Mean?

Battle-Tested and Ready for Production

Running Side-by-Side with TypeScript 6.0

Nightly Builds and @typescript/native-preview

Custom Scaling: Parallelization and Controls

Type-Checker Parallelization

Project Reference Builder Parallelization

Single-Threaded Mode

Improved --watch Mode

Updates Since 5.x, and New Behaviors from 6.0

Template Literal Types Now Preserve Unicode Code Points

JavaScript Differences

Editor Experience

TypeScript and Embedded Languages

The Road Forward