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

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-20250404000352 was published on 2025-04-04. Its manifest declares 1 runtime dependency 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-20250404000352 · Latest release

Package specifications

Version0.0.0-test-20250404000352
License declarationApache-2.0
Published2025-04-04T00:04:08.343Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size55.85 KiB
Published file count60
Package typecommonjs
ES module entryNot declared
Default entryNot declared
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies278
Repository stars255
Repository forks121

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

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

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