Migrating to TypeScript?
See original GitHub issueGreat work!
Any interest in migrating to TypeScript? Pros and Cons?
I took a first step stab at it here. https://github.com/chauey/openapi-codegen
With Visual Studio Code, to run
- ctrl ` (to open terminal)
- npm install
- ctrl-shift-b -> “tsc: build”
- f5 (to debug with default params in .vscode/launch.json)
I wonder how best to keep things in sync if no migration to TypeScript but I want to continue to use TypeScript.
Next step I think would be to add interface for the models and remove any “any” types.
Thoughts?
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (9 by maintainers)
Top Results From Across the Web
Documentation - Migrating from JavaScript - TypeScript
At this point, you're probably ready to start using TypeScript files. The first step is to rename one of your .js files to...
Read more >Migrating millions of lines of code to TypeScript - Stripe
An incremental migration to TypeScript would force developers to work in both languages to accomplish common tasks.
Read more >A simple guide for migrating from JavaScript to TypeScript
When migrating over to TypeScript, one basic thing to keep in mind is TypeScript files have a .ts extension instead of .js ....
Read more >10 Strategies for migrating to TypeScript - Exploring JS
Start your migration with experiments: Play with your code base and try out various strategies before committing to one of them. · Then...
Read more >ts-migrate: A Tool for Migrating to TypeScript at Scale - Medium
Migration at scale is a complex task, and we explored a couple of options for moving from JavaScript to TypeScript: 1) Hybrid migration...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@MikeRalphson You must (for a definition of it) try Typescript, it really improves the dev experience. Also, (biased & personal) I tend to discard non Typescript projects as I find using Typescript is a good indicator of verifiable quality (not saying non Typescript projects are all of bad quality, here).
I meant, coffeescript was all the rage at one time, and was going to be the future of typed javascript, but now it’s practically dead.
I may try Typescript on some new project to try it out, but at the moment, nothing above is compelling me to move this project to it.