6.0 Deprecation Candidates

[RyanCavanaugh]

• Change the default rootDir to the location of the tsconfig.json (i.e. "."). This can be safely transitioned by having a warning at 6.0 if the rootDir we would have inferred doesn't match ".".

[RyanCavanaugh]

This is a tracking issue, so I'm locking this since I don't want a flood of "You should deprecate X" comments here. Post on the relevant thread for X instead, and if it seems like a possible fit for deprecation, we'll cross-link here.

[andrewbranch]

Module stuff:

• Deprecate conditional imports/exports fallback lookups
• Deprecate --moduleResolution classic
  • Change default moduleResolution for --module es2015 et al.
• Deprecate --moduleResolution node/node10
  • Change default moduleResolution for --module commonjs
• Deprecate allowSyntheticDefaultExports and esModuleInterop (make the latter always true)

[DanielRosenwasser]

We've talked quite a bit about moving strictNullChecks and noImplicitAny to being on by default. In order to transition our userbase, would it make sense to require them to either

• set to true either explicitly or implicitly (i.e. via --strict) or
• explicitly be set to false?

[RyanCavanaugh]

tsc foo.ts not applying tsconfig.json - See #57159 and many others

[RyanCavanaugh]

no-default-lib

[RyanCavanaugh]

amd-module

[RyanCavanaugh]

Mix tsconfig.json with extra files #27379

[sheetalkamat]

May be default types should be [] verses undefined

[RyanCavanaugh]

#58453 error on asserts in import statements

[RyanCavanaugh]

Multi-file global value namespaces

[andrewbranch]

--rootDirs? https://www.typescriptlang.org/tsconfig/#rootDirs

[andrewbranch]

Import assertions should start erroring (saying to use import attributes instead) in --module esnext and --module preserve. They will already error in --module nodenext when #60534 is done.

[andrewbranch]

I forgot to include --baseUrl earlier

[RyanCavanaugh]

module Foo { (synonym of namespace Foo {), see #61450 for RWC results