In TypeScript 7.0, we have no plans to reimplement --moduleResolution classic - its behavior does not model any resolution system in widespread use, and at best it's just an approximation that avoids Node.js style resolution. Users will be better of using nodenext or bundler if necessary.
In TypeScript 6.0, --moduleResolution classic will be deprecated. Users enabling it will get an error message that can only be suppressed via --ignoreDeprecations.
In 7.0, we are thinking the default will be bundler unless there is an appropriate moduleResolution target that matches a given --module target.
See more on deprecations/changes for 6.0/7.0 in #54500.
In TypeScript 7.0, we have no plans to reimplement
--moduleResolution classic- its behavior does not model any resolution system in widespread use, and at best it's just an approximation that avoids Node.js style resolution. Users will be better of usingnodenextorbundlerif necessary.In TypeScript 6.0,
--moduleResolution classicwill be deprecated. Users enabling it will get an error message that can only be suppressed via--ignoreDeprecations.In 7.0, we are thinking the default will be
bundlerunless there is an appropriatemoduleResolutiontarget that matches a given--moduletarget.See more on deprecations/changes for 6.0/7.0 in #54500.