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

next-artemis

v0.0.4

Published

A companion for your Next.js app using Apollo

Downloads

11

Readme

next-artemis

A companion for your Apollo app with Next.js

Features

  • Built with TypeScript for extended stability
  • Built also with Jest and Enzyme for unit testing
  • Apollo cache hydration + single app connections (a single connection will only have a single client)
  • Exported types and interfaces
  • Hooks into NextJS's configuration object

Usage

Artemis will hook into NextJS's getConfig() object. You can provide it via next.config.js:

module.exports = withSass(withTypescript({
    publicRuntimeConfig: {
        graphQLEndpoint: // your GraphQL endpoint,
    }
}));

If no object is provided, Artemis will fall back to localhost:5000/graphql.

WithArtemis is next-artemis's default export. You import this wherever you'd like to use the client. It passes down a prop called artemisClient to your wrapped component, which is a wrapped instance of ApolloClient.

In _app.tsx:

import App, { Container } from "next/app";
import React from "react";
import { ApolloProvider } from "apollo-provider";
import { ApolloClient } from "apollo-client";
import WithArtemis, { ArtemisState } from "next-artemis";

interface AppProps {
    artemisClient: ApolloClient<ArtemisState<any>>; //where <any> is your apollo client shape
}

class MyApp extends App<AppProps> {
    public render () {
        const { Component, pageProps, router, artemisClient } = this.props;
        return (
            <ApolloProvider client={artemisClient}/>
                <Container>
                    <Component {...pageProps}/>
                </Container>
            </ApolloProvider>
        );
    }
}

export default WithArtemis(MyApp);

Next-Artemis also exports an initArtemis function that you can call with your initial state to hydrate Apollo's cache.

Usage:

import { initArtemis } from "next-artemis";

const client = initArtemis({
    data: {
        foo: "bar",
        baz: "foo"
    }
});

You'd import this and use it wherever you'd use an instance of ApolloClient.

Roadmap

  • Improve unit tests
  • Create an Artemis Provider that handles client linking for you

This package is currently under development - Pull Requests are greatly appreciated!