@itwin/core-common 3.0.0-dev.100

iTwin.js components common to frontend and backend

@itwin/core-common@3.0.0-dev.100 was published on 2021-10-27. Its manifest declares 4 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.

Deprecated: This package has reached end of life and is no longer maintained. Please refer to the iTwin.js support policy (https://www.itwinjs.org/learning/api-support-policies/) and the 4.0 changelog (https://www.itwinjs.org/changehistory/4.0.0) for upgrade guidance.

All @itwin/core-common versions · Permanent reference to 3.0.0-dev.100 · Latest release

Package specifications

Version3.0.0-dev.100
License declarationMIT
Published2021-10-27T05:30:19.125Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count4
Peer requirement count3
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size9187.16 KiB
Published file count1189
Package typeNot declared
ES module entrylib/esm/core-common.js
Default entrylib/cjs/core-common.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies4
Repository stars738
Repository forks248

Install @itwin/core-common 3.0.0-dev.100

npm install @itwin/core-common@3.0.0-dev.100
pnpm add @itwin/core-common@3.0.0-dev.100
yarn add @itwin/core-common@3.0.0-dev.100

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