captbaritone
chore: make typescript a peerDependency
Pinning the internal version can cause havok when running npx grats, due various flags/configurations of tsconfig.json not being supported by older TS versions.
Deploy Preview for grats failed. Why did it fail? →
| Name | Link |
|---|---|
| Latest commit | d8cf01e26fbe1b768cdb18c236b35750c9ae640e |
| Latest deploy log | https://app.netlify.com/projects/grats/deploys/686fdfe26bee230008931520 |
![netlify[bot] avatar](https://avatars.githubusercontent.com/in/13473?v=4 "Published by a pub.dev verified publisher"){kind=small}
Sorry I missed this. I know the problem you're highlighting, but I'm a little hesitant to take this on since there are places where we do poke (lightly) into private TypeScript APIs and I don't know that we can reliably trust those to behave stably on all versions of TypeScript.
That said, I like the idea of making both graphql and typescript peer dependencies long term since one of the values of Grats is that it has so few dependencies and the ones that are actually heavy are surely already dependencies you have.
I think a prerequisite for this would be to get our CI tests to run with several versions of TypeScript so that we can validate that we actually can safely run with arbitrary versions of TypeScript.
