apollo-server-koa 2.2.5

Production-ready Node.js GraphQL server for Koa

apollo-server-koa@2.2.5 was published on 2018-11-29. Its manifest declares 17 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.

Deprecated: The `apollo-server-koa` package is part of Apollo Server v2 and v3, which are now end-of-life (as of October 22nd 2023 and October 22nd 2024, respectively). This package's functionality is now found in the `@apollo/server` package. See https://www.apollographql.com/docs/apollo-server/previous-versions/ for more details.

All apollo-server-koa versions · Permanent reference to 2.2.5 · View npm registry JSON · Latest release

Package specifications

Version2.2.5
License declarationMIT
Published2018-11-29T11:46:05.779Z
Node.js requirement>=6
Type declarationsBundled declarations
Runtime dependency count17
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size56.44 KiB
Published file count22
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories1
Resolved graph dependencies256
Repository starsUnknown
Repository forksUnknown

Install apollo-server-koa 2.2.5

npm install apollo-server-koa@2.2.5
pnpm add apollo-server-koa@2.2.5
yarn add apollo-server-koa@2.2.5

Runtime dependencies

Peer requirements

  • graphql ^0.12.0 || ^0.13.0 || ^14.0.0

Optional dependencies

  • None declared

Resolved dependency graph

This deps.dev graph describes a generic 64-bit Linux environment, not your application lockfile.

How to interpret the specifications

Bundlephobia measurements use its standard package build and may exclude peer dependencies. Unpacked npm distribution size includes shipped files and is a different measurement. Module declarations do not prove tree-shaking or runtime compatibility.

Advisories apply to this package version directly; transitive dependencies need separate inspection. Repository signals describe the whole repository and are current observations, including on historical-version pages.

Known direct advisories

Evidence and freshness