@graphql-tools/prisma-loader 6.0.11

A set of utils for faster development of GraphQL tools

@graphql-tools/prisma-loader@6.0.11 was published on 2020-06-25. 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.

Deprecated: This package was intended to be used with an older versions of Prisma.\nThe newer versions of Prisma has a different approach to GraphQL integration.\nTherefore, this package is no longer needed and has been deprecated and removed.\nLearn more: https://www.prisma.io/graphql

All @graphql-tools/prisma-loader versions · Permanent reference to 6.0.11 · View npm registry JSON · Latest release

Package specifications

Version6.0.11
License declarationMIT
Published2020-06-25T22:42:34.679Z
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 size13.40 KiB
Published file count6
Package typeNot declared
ES module entryindex.esm.js
Default entryindex.cjs.js
Side effects declarationfalse
Direct advisories0
Resolved graph dependencies136
Repository starsUnknown
Repository forksUnknown

Install @graphql-tools/prisma-loader 6.0.11

npm install @graphql-tools/prisma-loader@6.0.11
pnpm add @graphql-tools/prisma-loader@6.0.11
yarn add @graphql-tools/prisma-loader@6.0.11

Runtime dependencies

Peer requirements

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