Search results

Always treat <code>.d.*.ts</code> files as commonjs-format modules for the purposes of import interop

Author: Team

Breaking ChangeWould introduce errors in existing codeWould introduce errors in existing code

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

For Milestone BugPRs that fix a bug with a specific milestonePRs that fix a bug with a specific milestone

Status: Open (in progress).

microsoft/TypeScriptnumber 59622

#59622 In microsoft/TypeScript;

· weswigham opened on Aug 13, 2024

Can’t resolve <code>@types</code> when vendoring dependencies for browser ESM imports

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

Needs ProposalThis issue needs a plan that clarifies the finer details of how it could be implemented.This issue needs a plan that clarifies the finer details of how it could be implemented.

Status: Open.

#50600 In microsoft/TypeScript;

· pehrlich2 opened on Sep 1, 2022

Remove the error on importing a json document in esm files in <code>moduleResolution: nodenext</code>

dependenciesPull requests that update a dependency filePull requests that update a dependency file

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

Status: Open.

#47819 In microsoft/TypeScript;

· weswigham opened on Feb 9, 2022

nodenext allows trailing slash module specifier to match <code>.</code> export

BugA bug in TypeScriptA bug in TypeScript

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

Status: Open.

#47805 In microsoft/TypeScript;

· andrewbranch opened on Feb 8, 2022

· 

Backlog

Evaluate popular packages that have <code>exports</code> fields set but may not be Node ESM-ready for TypeScript

Community ToolingThis might be better handled by tooling from the community instead of built into TypeScriptThis might be better handled by tooling from the community instead of built into TypeScript

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

RescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone

Status: Open.

#47792 In microsoft/TypeScript;

· DanielRosenwasser opened on Feb 7, 2022

· 

TypeScript 5.7.0

package.json diagnostics in <code>--module nodenext</code>

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

In DiscussionNot yet reached consensusNot yet reached consensus

RescheduledThis issue was previously scheduled to an earlier milestoneThis issue was previously scheduled to an earlier milestone

SuggestionAn idea for TypeScriptAn idea for TypeScript

Status: Open.

#46861 In microsoft/TypeScript;

· andrewbranch opened on Nov 18, 2021

· 

TypeScript 5.7.0

esModuleInterop should work even when compiling to esnext modules

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

In DiscussionNot yet reached consensusNot yet reached consensus

SuggestionAn idea for TypeScriptAn idea for TypeScript

Status: Open.

#22851 In microsoft/TypeScript;

· jamiebuilds opened on Mar 24, 2018

Bug: Incorrect module resolution for "valid" ES2015 specifiers with hashes and/or search parameters

Awaiting More FeedbackThis means we'd like to hear from more people who would be helped by this featureThis means we'd like to hear from more people who would be helped by this feature

Domain: ES ModulesThe issue relates to import/export style module behaviorThe issue relates to import/export style module behavior

SuggestionAn idea for TypeScriptAn idea for TypeScript

Status: Open.

#22689 In microsoft/TypeScript;

· SMotaal opened on Mar 19, 2018