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 🙏

© 2026 – Pkg Stats / Ryan Hefner

apollo-codegen-webpack-plugin

v0.5.1

Published

This plugin helps you run the [apollo-tooling](https://github.com/apollographql/apollo-tooling#apollo-clientcodegen-output) module using webpack without having to wire them together in a single process or running the two processes manually. It also handle

Readme

Apollo Codegen Webpack Plugin

This plugin helps you run the apollo-tooling module using webpack without having to wire them together in a single process or running the two processes manually. It also handles the extraction of a schema file for you to be used in apollo-cache's IntrospectionFragmentMatcher for instance. It does this by attaching into webpack compilation hooks.

On startup this plugin will:

  • Extract schema file from endpoint
  • Do an initial codegen based on that schema.json on all the files that you target with the included option

On a file change this plugin will:

  • Generate types based on the schema.json for changed files that match the included option

Installing 💾

npm i -D apollo-codegen-webpack-plugin

Or when using yarn:

yarn add -D apollo-codegen-webpack-plugin

Usage 🕹

// in your webpack.config.js

const ApolloCodegenWebpackPlugin = require('apollo-codegen-webpack-plugin');

module.exports = {
    // ... your config
    plugins: [
        // ... your other plugins
        new ApolloCodegenWebpackPlugin({
            // ... your options
        }),
    ],
}

Options ⚙

This plugin passes your provided options in apollo:codegen. For a list of supported options, see: https://github.com/apollographql/apollo-tooling#apollo-clientcodegen-output

Note: the [OUTPUT] positional is supported by passing an 'output' option to this plugin

Note: the localSchemaFile option is also used to determine where to place the generated schema file.

Note: valueless flags can be used by giving them a value of true. examples: "addTypename: true", "outputFlat: true"

Additional options

A additional options are also supported, these are:

critical

Type: Boolean - Default: false

When this option is set to true, the plugin will exit with exit code 1 when an error occurs when generating the types or downloading the schema. This is useful when you want to use this plugin to also check your queries on a production build.

skipSSLValidation

Type: String

This option maps to service:download option.

Multiple installations of graphql 📦

You may end up with some errors in your console about running multiple installations of graphql. To fix this for yarn, you can stick this in your package.json:

"resolutions": {
    "graphql": // your desired version
}

To fix this with npm, you can look at an equivalent like: https://github.com/rogeriochaves/npm-force-resolutions