apollo-server-plugin-base 0.6.4

Apollo Server plugin base classes

apollo-server-plugin-base@0.6.4 was published on 2019-09-01. Its manifest declares 1 runtime dependency and 1 peer requirement. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=6.

Deprecated: The `apollo-server-plugin-base` 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-plugin-base versions · Permanent reference to 0.6.4 · Latest release

Package specifications

Version0.6.4
License declarationMIT
Published2019-09-01T21:47:02.037Z
Node.js requirement>=6
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size7.37 KiB
Published file count9
Package typeNot declared
ES module entryNot declared
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies119
Repository starsUnknown
Repository forksUnknown

Install apollo-server-plugin-base 0.6.4

npm install apollo-server-plugin-base@0.6.4
pnpm add apollo-server-plugin-base@0.6.4
yarn add apollo-server-plugin-base@0.6.4

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.

Evidence and freshness