v0.2.1

Breaking changes

When trying to import from remix-graphql, the library will now throw an error. Using the default import might break the browser bundle because remix-graphql only works on the server. To fix this, import from remix-graphql/index.server.

Migration guide

Make sure that all imports from remix-graphql look like this:

- import { ... } from "remix-graphql";
+ import { ... } from "remix-graphql/index.server";

v0.1.3

New features

• There's a new function sendGraphQLRequest. It can be used to send GraphQL requests to a remote API from a loader or action function. Like processGraphQLRequest, it automatically derived variables from params and form data.
• There's a new example app that shows how to use sendGraphQLRequest with the GitHub GraphQL API.

Other improvements

• There was a duplicate link in the README that was removed.

v0.1.2

New features

• The new function processRequestWithGraphQL allows you to handle loader and action requests using GraphQL with ease.
• All exported functions now allow passing a context object which will be included in the execution context.

Other improvements

• There is a new section in the README about how to automatically generate types for the result of GraphQL operations
• The whole jokes-tutorial example was rewritten to include a GraphQL API that handles authentication and the loading, creation, and deletion of jokes, and it now uses processRequestWithGraphQL from remix-graphql in all loader and action functions.

v0.1.0

Breaking changes

• Avoid breaking the browser bundle by importing from remix-graphql/index.server instead of remix-graphql

Migration guide

Update all imports from remix-graphql like this:

- import { ... } from "remix-graphql";
+ import { ... } from "remix-graphql/index.server";

v0.0.1

Initial release 🥳

New features

• Added function createLoaderFunction that handles GraphQL requests for GET requests to a resource route
• Added function createActionFunction that handles GraphQL requests for POST requests to a resource route