It’s a nice but awful problem. I don’t see any way around it. You make something great that people depend on then you are more likely to break people if you make changes. Won’t Rome eventually get this if it grows enough?
-
-
-
No because Rome will offer little integration with other tools because it’s not necessary
- 2 more replies
New conversation -
-
-
This Gatsby plugin doesn't even depend on TypeScript. It simply adds Babel's TypeScript plugin to the wepback config. What exactly will the TS team need to coordinate in this case?
-
If they want to add syntax, or make a breaking change, then all tools someone uses needs to be upgraded at once. Which means in order for a new TS major to be usable then all these rando tools need to be upgraded out of the gate.
- 1 more reply
New conversation -
-
-
I think there are mainly three core things we put time into to make sure they are not broken on TS releases: - typescript’s compiler API - babel’s typescript - typescript-eslint I think in a lot of the ‘now with TS built-in’ cases, it’s really about our babel support
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I wouldn’t say they need to but it’s pretty nice of them to
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I don’t see why it’s a problem for TS maintainers, they have lots of users, they have to handle that difficulty already, no matter on what tools brings TS by default. It’s more a problem for gatsby TS users who would have to update TS at the same time they update gatsby.
-
And maybe they can override the Gatsby typescript plugin.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
he/him 
New in Gatsby: Native
Gatsby core now includes gatsby-plugin-typescript so your project will build TypeScript and TSX files by default!