-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Migration suggestions after *introducing* a .ts file #24714
Copy link
Copy link
Open
Labels
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 featureNeeds 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.SuggestionAn idea for TypeScriptAn idea for TypeScript
Metadata
Metadata
Assignees
Labels
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 featureNeeds 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.SuggestionAn idea for TypeScriptAn idea for TypeScript
After I brought #24713 up with @chrisdias, he mentioned his thinking was more about the "I'm going to introduce a
.tsfile into a JS project" scenario. I think once you have some.tsfiles around a project, you're going to want to migrate the.jsfiles eventually too, so both scenarios are valid.But things we could do include
tsconfig.json@typesdependencies for packages that need them.@mjbvz @amcasey