@aws-amplify/plugin-types 0.0.0-test-20240815221003

This is a **types only** package that is used to facilitate dependency injection patterns across the codebase. Components can declare that they need an instance of a certain type that comes from this package and another component can provide the implement

@aws-amplify/plugin-types@0.0.0-test-20240815221003 was published on 2024-08-15. Its manifest declares 0 runtime dependencies and 3 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

All @aws-amplify/plugin-types versions · Permanent reference to 0.0.0-test-20240815221003 · Latest release

Package specifications

Version0.0.0-test-20240815221003
License declarationApache-2.0
Published2024-08-15T22:10:15.162Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size44.75 KiB
Published file count48
Package typecommonjs
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies0
Repository stars255
Repository forks121

Install @aws-amplify/plugin-types 0.0.0-test-20240815221003

npm install @aws-amplify/plugin-types@0.0.0-test-20240815221003
pnpm add @aws-amplify/plugin-types@0.0.0-test-20240815221003
yarn add @aws-amplify/plugin-types@0.0.0-test-20240815221003

Runtime dependencies

  • None declared

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