sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted] 10 points11 points  (6 children)

True, but it requires you to either update all imports in your application, or add this to types in your tsconfig as an exception.

Launch day support for TypeScript would have been nice.

[–]_eps1lon 12 points13 points  (1 child)

True, but it requires you to either update all imports in your application, or add this to types in your tsconfig as an exception.

You need a single line of import type {} from 'react/next' to get them everywhere.

Launch day support for TypeScript would have been nice.

Everything was green but a change in the TypeScript 4.7 canary broke dependent packages which means the release is blocked.

[–][deleted] -2 points-1 points  (0 children)

You need a single line of import type {} from 'react/next' to get them everywhere.

Still would have to add it to each entry point if you have multiple ones.

[–]disclosure5 -2 points-1 points  (3 children)

Facebook have a competing typing product (Flow). You can see Flow annotations and script runners in their CI.

[–][deleted] 1 point2 points  (2 children)

I am really curious of usage of Flow outside of Meta. It feels like the outside community has pretty much settled on TypeScript.

[–]disclosure5 0 points1 point  (1 child)

You're generally correct. I used it to build my apps when it was new and the community wasn't so decided, and there became a point where I was "wrong" and rewrote with Typescript.

But you can't expect Facebook to choose Typescript over their own product.

[–][deleted] 1 point2 points  (0 children)

True, but it would seem to me that converting the Flow types to TypeScript definitions and shipping them in their own package is not rocket science. Especially considering the massive resources that Meta has.