This article provides a beginner-friendly guide to getting started with Node.js, GraphQL, and TypeScript. Luka walks through setting up a basic GraphQL server with Node.js and TypeScript, including defining schemas, resolvers, and queries. With clear explanations and step-by-step examples, this guide is perfect for anyone new to these technologies. Whether you're a seasoned developer looking to learn something new or a beginner just starting, this article is a great resource for getting started with Node.js, GraphQL, and TypeScript.
This article discusses whether or not introspection in GraphQL should be disabled for production environments, highlighting potential security risks associated with allowing introspection, such as exposing sensitive information or allowing attackers to explore the schema. The article also provides alternative solutions for securing production environments and discusses the benefits of introspection for development and testing. With clear explanations and examples, this article is helpful for those looking to make informed decisions about introspection in GraphQL.
A list of 10 GraphQL developer tools that can help make development easier. Prithwish highlights each tool's features and benefits, such as GraphQL Playground for testing and debugging queries, GraphQL Code Generator for automatically generating code from a schema, and Apollo Client DevTools for debugging Apollo Client applications. With practical examples and links to documentation, this guide is a helpful resource for anyone looking to streamline their GraphQL development workflow.
Tools & Open Source
graphql-web-lite provides an alias package that can be swapped in for the standard graphql package in client-side applications. It aims to reduce the size of imports that are in common use by GraphQL clients and users, while still providing most graphql exports that are used in other contexts.
Having made a bet on GraphQL Federation 3 years ago, Netflix knows a thing or two about the potential pitfalls. Stephen Spalding walks us through a couple of these pitfalls, which he calls Microservice Madness and Schema Anarchy.