Skip to content
This repository has been archived by the owner on Jan 5, 2022. It is now read-only.

There are (probably) multiple steps in the lifecycle of a TS project #4

Open
orta opened this issue Apr 22, 2019 · 2 comments
Open

There are (probably) multiple steps in the lifecycle of a TS project #4

orta opened this issue Apr 22, 2019 · 2 comments

Comments

@orta
Copy link
Owner

orta commented Apr 22, 2019

JS -> TS -> TS (strict)
@orta
Copy link
Owner Author

orta commented Apr 22, 2019

How could tooling help go through each transition?

@orta
Copy link
Owner Author

orta commented Apr 23, 2019 •
edited
Loading

Screen Shot 2019-04-23 at 12 39 46 PM

More like there are four stages:

  • Step 1 is effectively "free" - use VS Code and get a subset of TS tooling
  • Step two is add a jsconfig.json and put // @ts-enable in the top of your files, cheap, and only available per-file
  • Step three is add a tsconfig.json and change *.js -> *.ts (which feels like the biggest step)
  • Step four is hard to do in established projects, but can be the most valuable from a safety perspective but less valuable from a tooling one

@orta orta mentioned this issue Apr 24, 2019
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@orta