Topic will be on Why, what and how of typescript with GraphQL. Idea is to provide audience idea on how to use GraphQl with Typescript, how to automatically generate typed document nodes and fragments that can help with the following Static Typing: TypeScript provides static typing, which helps catch type-related errors during development. With GraphQL, where types play a crucial role in defining the schema and handling data, having type checking at compile-time can prevent many runtime errors. Type Inference: TypeScript can infer types based on your code, reducing the need for explicit type annotations. This feature is particularly useful when working with GraphQL schemas and queries, where types are often nested and complex. IDE Support: TypeScript offers excellent IDE support with features like autocompletion, type checking, and inline documentation. When working with GraphQL, which involves defining types and writing queries, this support can significantly improve productivity. Enhanced Development Experience: TypeScript's features such as code navigation, refactoring tools, and error highlighting contribute to a smoother development experience. This is especially beneficial when building GraphQL APIs, which often involve handling various types of data and operations. Maintainability: With TypeScript, codebases tend to be more maintainable due to better type safety and clearer interfaces. When working with GraphQL schemas and resolvers, having types explicitly defined can make the codebase easier to understand and modify over time. Ecosystem Compatibility: Many libraries and tools in the GraphQL ecosystem provide TypeScript support out of the box or have TypeScript typings available. This ensures compatibility and seamless integration when using TypeScript with GraphQL-related packages. Overall, using TypeScript with GraphQL can lead to more robust, maintainable, and developer-friendly codebases. I have used them extensively on our observability platforms in salesforce.