@arcgis/components-controllers 4.34.0-next.115

Controllers are a code-reuse pattern for Stencil and Lit Web Components. They also improve Developer Experience of writing Web Components

@arcgis/components-controllers@4.34.0-next.115 was published on 2025-08-29. Its manifest declares 3 runtime dependencies and 0 peer requirements. Type declarations are bundled according to the package metadata. No Node.js engine requirement is declared in this manifest.

Deprecated: This version is no longer supported. Upgrade to @latest

All @arcgis/components-controllers versions · Permanent reference to 4.34.0-next.115 · View npm registry JSON · Latest release

Package specifications

Version4.34.0-next.115
License declarationSEE LICENSE IN LICENSE.md
Published2025-08-29T04:46:59.590Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count3
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9.57 KiB
Published file count7
Package typemodule
ES module entrydist/index.js
Default entrydist/index.cjs
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies10
Repository starsUnknown
Repository forksUnknown

Install @arcgis/components-controllers 4.34.0-next.115

npm install @arcgis/components-controllers@4.34.0-next.115
pnpm add @arcgis/components-controllers@4.34.0-next.115
yarn add @arcgis/components-controllers@4.34.0-next.115

Runtime dependencies

Peer requirements

  • None declared

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