You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 3, 2024. It is now read-only.
Not sure if this should be the way to move forward. This will allow us to provide a smoother experience for 100% typescrip codebase, i.e generating typings for queries in both gatsby-node and src/**/*.ts{x}.
Current problems:
Gatsby don't watch gatsby-node, or files outside of src
Typegen doesn't happen until onPostBootstrap. If user changes their query in gatsby-node and the new type is not yet generated, error will be thrown & prevent a new build.
We don't have to go heavy on this, i.e creating a separate process. Perhaps a webpack plugin? Not sure yet ... need some more thinking...
Also, I wish we knew a bit more about Gatsby's plan on supporting TS in v3! :)
The text was updated successfully, but these errors were encountered:
Not sure if this should be the way to move forward. This will allow us to provide a smoother experience for 100% typescrip codebase, i.e generating typings for queries in both
gatsby-node
andsrc/**/*.ts{x}
.Current problems:
gatsby-node
, or files outside ofsrc
onPostBootstrap
. If user changes their query in gatsby-node and the new type is not yet generated, error will be thrown & prevent a new build.We don't have to go heavy on this, i.e creating a separate process. Perhaps a webpack plugin? Not sure yet ... need some more thinking...
Also, I wish we knew a bit more about Gatsby's plan on supporting TS in v3! :)
The text was updated successfully, but these errors were encountered: