Yoga Context

Yoga Context is an important part of building production-ready GraphQL systems. This lesson explains what yoga context means, how it works, and how to apply it with practical examples you can reuse.

Yoga Context Overview

Yoga Context is a building block you will reach for often in GraphQL. It keeps related logic together and makes your intent obvious to reviewers and future maintainers.

When you learn yoga context properly, you avoid the guesswork that leads to bugs and rework. The example below shows the shape you will use in most real GraphQL projects.

import { createYoga, createSchema } from 'graphql-yoga';
import { createServer } from 'node:http';

const yoga = createYoga({
  schema: createSchema({ typeDefs, resolvers }),
});
createServer(yoga).listen(4000);

GraphQL Yoga is a batteries-included server that runs the same schema and resolvers.

Yoga Context Example

const typeDefs = gql`
  type Query { hello: String! }
`;
const resolvers = { Query: { hello: () => 'world' } };
const server = new ApolloServer({ typeDefs, resolvers });

Start from a minimal Yoga Context example and grow it only as needed.
Keep configuration explicit so Yoga Context behaves the same in every environment.
Name things clearly so teammates understand your Yoga Context at a glance.
Add tests around Yoga Context early to lock in expected behaviour.

GraphQL Cheatsheet

Quick GraphQL reference related to yoga context.

Concept	Example	Purpose
Schema	`type Query { user(id: ID!): User }`	Define the API shape
Resolver	`Query: { user: (_, { id }) => ... }`	Provide field data
Query	`query { user(id: 1) { name } }`	Read exactly what you need
Mutation	`mutation { createUser(input) { id } }`	Change data
Subscription	`subscription { postAdded { id } }`	Real-time updates
Context	`context: ({ req }) => ({ user })`	Auth and shared state
DataLoader	`loader.load(id)`	Batch to avoid N+1

How Yoga Context Works in GraphQL

Yoga Context fits into GraphQL's model of a single typed schema that clients query for exactly the data they need. The server resolves each requested field through resolver functions.

GraphQL Yoga is a batteries-included server that runs the same schema and resolvers.

The schema is the contract between client and server.
Resolvers fetch data field by field, including nested types.
Clients request only the fields they use, avoiding over-fetching.
Context carries auth and shared services into every resolver.

Practical Guidance for Yoga Context

In production, yoga context should be efficient and secure. Batch data access with DataLoader, guard resolvers with authorization, and limit query depth and complexity.

Concern	Recommendation
N+1 queries	Batch with DataLoader
Security	Auth in context, depth/complexity limits
Errors	Typed GraphQLError with extension codes
Performance	Cache and paginate large lists

Common Mistakes

Copying yoga context snippets without understanding what each line does.
Skipping error handling and edge cases when wiring up yoga context.
Leaving yoga context untested, so regressions slip into production.
Over-engineering yoga context before you actually need the extra flexibility.

Key Takeaways

Yoga Context is a core part of working effectively with GraphQL.
Start small and keep yoga context focused on a single responsibility.
Apply consistent patterns so yoga context scales across your project.
Test and document yoga context to keep it maintainable over time.

Pro Tip

Pair yoga context with automated tests from day one. It is far cheaper to catch GraphQL regressions in CI than in production.