@itwin/core-geometry 4.5.0-dev.30

iTwin.js Core Geometry library

@itwin/core-geometry@4.5.0-dev.30 was published on 2024-03-13. Its manifest declares 2 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 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 5.0 changelog (https://www.itwinjs.org/changehistory/5.0.0) for upgrade guidance.

All @itwin/core-geometry versions · Permanent reference to 4.5.0-dev.30 · Latest release

Package specifications

Version4.5.0-dev.30
License declarationMIT
Published2024-03-13T05:42:21.144Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count2
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size26624.45 KiB
Published file count1756
Package typeNot declared
ES module entrylib/esm/core-geometry.js
Default entrylib/cjs/core-geometry.js
Side effects declaration["./lib/esm/core-geometry.js"]
Direct advisories0
Resolved graph dependencies2
Repository stars738
Repository forks248

Install @itwin/core-geometry 4.5.0-dev.30

npm install @itwin/core-geometry@4.5.0-dev.30
pnpm add @itwin/core-geometry@4.5.0-dev.30
yarn add @itwin/core-geometry@4.5.0-dev.30

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