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

@apollo/server-integration-testsuite

v4.10.4

Published

Test suite for Apollo Server integrations

Downloads

475

Readme

Apollo Server Integration Testsuite

This package serves as a set of Jest tests for Apollo Server integration authors. Any Node package which functions as the HTTP (or HTTP framework) binding and Apollo Server can run these tests to ensure parity with the 1st party Express integration.

Note: this package is only intended for integration authors. If your project runs an Apollo Server instance, you probably shouldn't use this.

The version of this package will be published in lockstep with Apollo Server, so choose the same version of this package as the version of Apollo Server which you intend to support. The expected configuration for an integration should follow the pattern:

{
  "name": "my-server-integration",
  "devDependencies": {
    "@apollo/server": "4.1.0",
    "@apollo/server-integration-testsuite": "4.1.0"
  },
  "peerDependencies": {
    "@apollo/server": "^4.0.0"
  }
}

In the example above, the peerDependencies allow your configuration to be used with the full range of Apollo Server v4 packages. The devDependencies which your integration is built and tested against should stay up-to-date with the latest version of Apollo Server, and the server and testsuite packages should be in lockstep with each other.

This package imposes dependency requirements on your project, however it should only require they be installed as devDependencies:

  • @apollo/server's version must match the version of the test suite.
  • The test suite expects you to be running jest@28. It's possible that other versions of Jest may be compatible, but this use case is unsupported and might lead to unexpected behavior. It's fine for your project to use a testing framework other than Jest, but you'll still need to configure Jest in your project in order to run the test suite (so you'll have two test runners configured in your project). Because of this, we recommend using only Jest in your project for simplicity.
  • graphql must be installed in your project in peerDependencies and your version range should match that of @apollo/server. The test suite package's graphql dependency will match that of Apollo Server's.