Skip to content

Resolver improvements in next minor or major version #1756

Open
@cspotcode

Description

@cspotcode
Collaborator

Extracted from #1753

  • Auto-enable experimentalResolver in a few situations:

    • when using ESM
    • when using nodenext / node16
    • in next major, enable by default always?
  • Ensure experimentalResolver can be explicitly disabled via tsconfig.json.

  • rename experimentalResolver to resolver

    • continue to parse experimentalResolver for backwards-compat
  • Ensure new resolver works with yarn pnp

    • I have notes in development-docs. We can detect PNP API in runtime and call out to it only for certain specifiers
  • Auto-enable esm in CLI?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

      Development

      No branches or pull requests

        Participants

        @cspotcode

        Issue actions

          Resolver improvements in next minor or major version · Issue #1756 · TypeStrong/ts-node