Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6.0 Deprecation Candidates #54500

Open
RyanCavanaugh opened this issue Jun 2, 2023 · 11 comments
Open

6.0 Deprecation Candidates #54500

RyanCavanaugh opened this issue Jun 2, 2023 · 11 comments
Labels
Meta-Issue An issue about the team, or the direction of TypeScript

Comments

@RyanCavanaugh
Copy link
Member

RyanCavanaugh commented Jun 2, 2023

  • 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 RyanCavanaugh added the Meta-Issue An issue about the team, or the direction of TypeScript label Jun 2, 2023
@RyanCavanaugh
Copy link
Member Author

RyanCavanaugh commented Jun 2, 2023

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.

@microsoft microsoft locked and limited conversation to collaborators Jun 2, 2023
@andrewbranch
Copy link
Member

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
Copy link
Member

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
Copy link
Member Author

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

@RyanCavanaugh
Copy link
Member Author

no-default-lib

@RyanCavanaugh
Copy link
Member Author

amd-module

@RyanCavanaugh
Copy link
Member Author

Mix tsconfig.json with extra files #27379

@sheetalkamat
Copy link
Member

May be default types should be [] verses undefined

@RyanCavanaugh
Copy link
Member Author

#58453 error on asserts in import statements

@RyanCavanaugh
Copy link
Member Author

Multi-file global value namespaces

@andrewbranch
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Meta-Issue An issue about the team, or the direction of TypeScript
Projects
None yet
Development

No branches or pull requests

4 participants