ts-migrate VS DefinitelyTyped

Update tsconfig. Replace the content of tsconfig.json with the values from tsconfig.base.json.

Airbnb converted many millions of lines gradually using automation and wrote about it:

https://medium.com/airbnb-engineering/ts-migrate-a-tool-for-...

And also open sourced the tooling:

https://github.com/airbnb/ts-migrate

Are you migrating with ts-migrate?

When you migrate your entire project over to TypeScript, errors like "undefined is not a function", syntax errors, or reference errors should no longer exist in your codebase. Thankfully, this is not as daunting as it sounds. Migrating your entire Node.js application to TypeScript can be done incrementally so that you can start reaping the rewards immediately in crucial parts of the codebase. You can also adopt a tool like ts-migrate if you intend to perform the migration in one go.

Flow to ts — helps to produce raw migration from Flow to TS files and reduces monkey job. TS migrate — helps convert JS files to Typescript files. A great introduction can be found here.

💡 I typed it using ts-migrate ts-migrate is a tool I strongly recommend. It's been developed by Airbnb to help to migrate easily JavaScript projects to TypeScript.

When you decide to migrate, I recommend checking https://github.com/airbnb/ts-migrate may speed few migration steps (but it wont solve missing types/interfaces)

You can use AirBnb's ts-migrate tool or try a more direct tactic following the Migrating from JavaScript guide.

Take a look at https://github.com/airbnb/ts-migrate

Sometimes, the community will provide unofficial type definitions. You can find it in the DefinitelyTyped repository (https://github.com/DefinitelyTyped/DefinitelyTyped), or search for @types/library-name on GitHub.

https://github.com/DefinitelyTyped/DefinitelyTyped/commit/4b...

It's still there to this date, but I've lost my TS port in the sands of time.

> I really loved PHP, but now with go+templ (https://templ.guide) I personally don't have a use-case for PHP anymore, but that doesn't mean it's irrelevant for the world.

This is the first time I've heard of Templ. It looks cool and it was really easy to set up. Apparently there are IDE extensions to enable syntax highlighting and HTML auto-completion, but is there a way to type check the templates? One of the things I love about JSX as a templating language is that errors in your markup get reported as type errors [1]. If I write `` instead of `` and run `tsc --noEmit --watch`, TypeScript will complain until I fix the issue. You can even extend the types to support your own HTML custom elements.

[1] https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

Prior to React 18, it used to include an implicit children prop, making it suitable for components expected to have children. For a long time, though, the implicit children prop type has been removed according to React 18's type changes.

Additionally, because TypeScript has a well established and widely used install-base, there are already many different definition files in the wild for supporting non-TypeScript supporting projects. One of the more extensive collections of these typings lives at the DefinitelyTyped repository, which publishes the package's community typings under the package names @types/your-package-name (where your-package-name is the name of the project you're looking for typings of) that you can look for on your package manager.

View on GitHub

Firefox maintain a library for unified extension API https://github.com/mozilla/webextension-polyfill

Their type definition for HAR request isn't exported https://github.com/DefinitelyTyped/DefinitelyTyped/blob/mast...

type NumberOrString = number | string; type Status = "idle" | "loading" | "success" | "failure" // React useState, can receive a value or a function as parameter to serve as initial value. // https://github.com/DefinitelyTyped/DefinitelyTyped/blob/a03856975a17eba524739676affbf70ac4078176/types/react/v17/index.d.ts#L920 function useState(initialState: S | (() => S)): [S, Dispatch>];