@graphql-codegen/typed-document-node 2.2.11

GraphQL Code Generator plugin for generating ready-to-use TypedDocumentNode based on GraphQL operations

@graphql-codegen/typed-document-node@2.2.11 was published on 2022-05-09. Its manifest declares 5 runtime dependencies and 1 peer requirement. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @graphql-codegen/typed-document-node versions · Permanent reference to 2.2.11 · Latest release

Package specifications

Version2.2.11
License declarationMIT
Published2022-05-09T09:09:33.074Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count5
Peer requirement count1
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.75 KiB
Published file count6
Package typeNot declared
ES module entryindex.mjs
Default entryindex.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies182
Repository stars11265
Repository forks1402

Install @graphql-codegen/typed-document-node 2.2.11

npm install @graphql-codegen/typed-document-node@2.2.11
pnpm add @graphql-codegen/typed-document-node@2.2.11
yarn add @graphql-codegen/typed-document-node@2.2.11

Runtime dependencies

Peer requirements

  • graphql ^0.8.0 || ^0.9.0 || ^0.10.0 || ^0.11.0 || ^0.12.0 || ^0.13.0 || ^14.0.0 || ^15.0.0 || ^16.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.

OpenSSF repository checks

Provider assessment: 2026-08-24T00:00:00Z. These are repository checks, not a jsL maintenance score.

Code-Review3/10 — Found 6/20 approved changesets -- score normalized to 3
Dangerous-Workflow10/10 — no dangerous workflow patterns detected
Maintained10/10 — 30 commit(s) and 20 issue activity found in the last 90 days -- score normalized to 10
CII-Best-Practices0/10 — no effort to earn an OpenSSF best practices badge detected
Token-Permissions0/10 — detected GitHub workflow tokens with excessive permissions
Binary-Artifacts10/10 — no binaries found in the repo
Security-Policy0/10 — security policy file not detected
Pinned-Dependencies10/10 — all dependencies are pinned
License10/10 — license file detected
Branch-Protection0/10 — branch protection not enabled on development/release branches
Fuzzing0/10 — project is not fuzzed
SAST0/10 — SAST tool is not run on all commits -- score normalized to 0

Evidence and freshness