npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

babel-plugin-fetch-relay-schema

v0.1.2

Published

Fetch relay schema from a URL.

Downloads

26

Readme

babel-plugin-fetch-relay-schema

This plugin is a thin wrapper around babel-relay-plugin that fetches the graphql schema from a graphql server or from a schema file. You can get the schema via URL or path to the runtime schema.

Usage

Via GRAPHQL_URL

Set the environment variable GRAPHQL_URL to the fully qualified URL to the graphql endpoint before running babel. Fetching is synchronous and will fail with a timeout after 30 seconds.

For example:
GRAPHQL_URL=http://localhost:8000/graphql node start

Via GRAPHQL_PATH

Set the path to the file containing the graphql schema. This file must export ES5. This plugin will bail when there is a cycle in the dependencies – that is, if GRAPHQL_PATH=schema.js, you can transform schema.js and its dependencies without creating an infinite dependency loop.

For example:

/* schema.babel.js */
const query = new GraphQLObjectType({...});
const mutation = new GraphQLObjectType({...});
export default new GraphQLSchema({
	query,
	mutation,
});

/* schema.js */
require('babel-core/register');
Object.assign(exports, require('./schema.babel'));

Then run: GRAPHQL_PATH=./schema.js node start

When is best to use GRAPHQL_PATH and GRAPHQL_URL?

I suggest using the URL if you don't have a good reason to use the path. I use path option alongside my mock schema for a completely offline testable UI. For all other use cases (integration testing and final builds), I use the URL for the environment that the build will ultimately be run against.

Options

Schema cache time to live

You can set the environment variable GRAPHQL_SCHEMA_CACHE_TTL to the number of milliseconds the schema cache should stay. Only do this in development mode, as it will slow down builds.

GRAPHQL_SCHEMA_CACHE_TTL applies to both GRAPHQL_URL and GRAPHQL_PATH usages.