refactor(javascript): type the nodes the syntax parser builds - #22719

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Type generation now detects internal aliases and type parameters and adjusts generated signatures and types accordingly. Parser implementation and test annotations now use more specific node types. The parser runtime logic is unchanged.

Changes: Generated Declaration Handling

Layer / File(s)	Summary
Recognize internal types tooling/generate-types.js	New helpers detect internal aliases and constrained type parameters, identify qualifying written and resolved types, and widen literal constraints.
Apply internal-type rules to signatures tooling/generate-types.js	Symbol lookup falls back to the checker when declarations are absent. Parameter and return parsing substitutes any for qualifying written types and filters internal type parameters.
Map internal types during type parsing tooling/generate-types.js	Type parsing replaces internal type parameters with widened constraints and maps other qualifying internal types to any.

Parser Type Annotations

Layer / File(s)	Summary
Narrow parser annotations lib/javascript/regexp.js, lib/javascript/syntax-printer.js, test/unitCases/JavascriptSyntaxTree.unittest.js, test/unitCases/WebpackParser.unittest.js	Parser implementation and test JSDoc annotations use more specific parser node types. The regexp prototype assertion now includes the Parser type. Runtime parser behavior is unchanged.

Suggested labels: area: parser, area: types, area: tooling

Suggested reviewers: bjohansebas

Generated types may permit omission of a required argument. Correct the optionality inference or confirm the affected declarations before merging.

Pre-merge checks: 3 · 1

Failed checks: 1 inconclusive

Check name	Status	Explanation	Resolution
Title check		The title uses the required Conventional Commit form, refactor(javascript): subject, and accurately describes the changes. The branch prefix is not provided, so the required prefix match cannot be v…	Provide the branch name or branch prefix. Confirm that it matches the refactor title type.

Passed checks: 3 passed

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Title check

Explanation

The title uses the required Conventional Commit form, refactor(javascript): subject, and accurately describes the changes. The branch prefix is not provided, so the required prefix match cannot be verified.

• X
• Mastodon
• Reddit
• LinkedIn

@@           Coverage Diff           @@
##             main   #22719   +/-   ##
=======================================
  Coverage   96.44%   96.44%           
=======================================
  Files         776      776           
  Lines      135523   135540   +17     
  Branches    45661    45668    +7     
=======================================
+ Hits       130704   130727   +23     
+ Misses       4819     4813    -6     

Flags with carried forward coverage won't be shown. Click here to find out more.

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

System calls cannot be consistently instrumented, so they are not included in the measure, which understates the real cost. Please switch to the Walltime instrument to accurately measure system calls.

Measurement and system calls

• benchmark "import-meta-glob", scenario '{"name":"mode-development","mode":"development"}'
• benchmark "wasm-modules-sync", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "no-concatenation", scenario '{"name":"mode-development","mode":"development"}'
• benchmark "devtool-source-map", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'
• benchmark "devtool-eval", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'
• benchmark "no-exports-analysis", scenario '{"name":"mode-development","mode":"development"}'
• benchmark "html-many-chunks", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'
• benchmark "json-modules", scenario '{"name":"mode-development-rebuild","mode":"development","watch":true}'
• benchmark "unsafe-cache", scenario '{"name":"mode-development","mode":"development"}'
• benchmark "resolve-unsafe-cache", scenario '{"name":"mode-development","mode":"development"}'
• …and 98 more

The flamegraph could not be generated because too much time was spent in runtime internals, making the visualization not useful for performance analysis.

• benchmark "wasm-modules-sync", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "lodash", scenario '{"name":"mode-development","mode":"development"}'
• benchmark "context-esm", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "concatenate-modules", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "common-libs", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "asset-modules-source", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "many-chunks-commonjs", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "css-modules", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "three-long", scenario '{"name":"mode-production","mode":"production"}'
• benchmark "loader-babel", scenario '{"name":"mode-development","mode":"development"}'
• …and 31 more

Some benchmarks with significant performance changes were compared across different runtime environments,
which may affect the accuracy of the results.

Open the report in CodSpeed to investigate