Port TypeScript PR #63054: Default types to [], support "*" wildcard

[Copilot]

Ports microsoft/TypeScript#63054. Changes default behavior: when types is unset, no @types packages are auto-discovered. Use types: ["*"] for the previous behavior.

Core Changes

• internal/core/compileroptions.go: Add UsesWildcardTypes() method—returns true if types contains "*"
• internal/module/resolver.go: Update GetAutomaticTypeDirectiveNames():
  • No wildcard → return types directly (or [] if nil)
  • Wildcard present → enumerate type roots, substitute "*" with discovered packages, deduplicate
• internal/checker/checker.go: Swap diagnostic message selection logic—now suggests adding to types when wildcards are NOT in use
  • Add getCannotResolveModuleNameErrorForSpecificModule() to detect Node.js core module imports and provide helpful error messages
  • Add "beforeEach" to test runner cases and "NodeJS" to node cases
• internal/compiler/fileInclude.go: Update automatic type directive file diagnostics to use new wildcard check

Example

// Old behavior (auto-discover all @types)
{ "compilerOptions": { } }

// New equivalent (explicit wildcard)
{ "compilerOptions": { "types": ["*"] } }

// Explicit subset only
{ "compilerOptions": { "types": ["node", "jest"] } }

// Mix explicit + wildcard
{ "compilerOptions": { "types": ["my-special-types", "*"] } }

Test Updates

• Baseline changes reflect updated error messages (TS2580 → TS2591 with types field instructions)
• Two fourslash tests added to failingTests.txt—depend on old auto-discovery behavior, will resolve when TypeScript submodule updates

Original prompt

Port microsoft/TypeScript#63054

Custom agent used: Strada to Corsa Port Expert
A Go and TypeScript expert who can easily figure out how to port PRs from one language to another

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[Copilot]

Pull request overview

This PR ports TypeScript PR #63054, implementing a breaking change where types defaults to [] (no auto-discovery) instead of discovering all @types packages. Users must explicitly use types: ["*"] to enable the previous auto-discovery behavior.

Changes:

• Added UsesWildcardTypes() method to check if types contains "*"
• Modified automatic type directive resolution to handle wildcard substitution
• Swapped diagnostic messages to recommend adding to types field when wildcards are NOT in use
• Updated test baselines to reflect new error messages (TS2580→TS2591, TS2581→TS2592, etc.)

Reviewed changes

Copilot reviewed 156 out of 156 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
internal/core/compileroptions.go	Added UsesWildcardTypes() helper method
internal/module/resolver.go	Updated GetAutomaticTypeDirectiveNames() to handle wildcard expansion and return empty array by default
internal/checker/checker.go	Inverted diagnostic message logic - now suggests adding to types when NO wildcard
internal/compiler/fileInclude.go	Updated to use UsesWildcardTypes() instead of checking Types != nil
testdata/baselines/reference/**	Updated test baselines reflecting new default behavior
internal/fourslash/_scripts/failingTests.txt	Removed 3 tests that now pass

[DanielRosenwasser]

Is this not missing an error update for core/built-in modules for Node.js? microsoft/TypeScript#63054 has

    function getCannotResolveModuleNameErrorForSpecificModule(moduleName: Expression): DiagnosticMessage | undefined {
        if (moduleName.kind === SyntaxKind.StringLiteral) {
            if (nodeCoreModules.has((moduleName as StringLiteral).text)) {
                if (usesWildcardTypes(compilerOptions)) {
                    return Diagnostics.Cannot_find_name_0_Do_you_need_to_install_type_definitions_for_node_Try_npm_i_save_dev_types_Slashnode;
                }
                else {
                    return Diagnostics.Cannot_find_name_0_Do_you_need_to_install_type_definitions_for_node_Try_npm_i_save_dev_types_Slashnode_and_then_add_node_to_the_types_field_in_your_tsconfig;
                }
            }
        }
        return undefined;
    }

[jakebailey]

@copilot Look into this; recheck the original PR for missing bits.

[Copilot]

@copilot Look into this; recheck the original PR for missing bits.

Added the missing getCannotResolveModuleNameErrorForSpecificModule function that checks if the imported module is a Node.js core module and returns the appropriate error message with wildcard-aware logic. Also added "beforeEach" to test runner cases and "NodeJS" to node cases. Fixed in 6a48e64.