@bentley/backend-itwin-client 2.18.0-dev.15

Clients for various Bentley Services used by iModel.js at the backend

@bentley/backend-itwin-client@2.18.0-dev.15 was published on 2021-06-24. Its manifest declares 13 runtime dependencies and 8 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is >=10.17.0 <15.0.

Deprecated: This package has reached end of life and is deprecated. Please refer to our support policy, https://www.itwinjs.org/learning/api-support-policies/, and changelog, https://www.itwinjs.org/v3/changehistory/3.0.0/#package-name-changes.

All @bentley/backend-itwin-client versions · Permanent reference to 2.18.0-dev.15 · Latest release

Package specifications

Version2.18.0-dev.15
License declarationMIT
Published2021-06-24T05:51:07.738Z
Node.js requirement>=10.17.0 <15.0
Type declarationsBundled declarations
Runtime dependency count13
Peer requirement count8
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size379.98 KiB
Published file count102
Package typeNot declared
ES module entryNot declared
Default entrylib/backend-itwin-client.js
Side effects declarationNot declared
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository starsUnknown
Repository forksUnknown

Install @bentley/backend-itwin-client 2.18.0-dev.15

npm install @bentley/backend-itwin-client@2.18.0-dev.15
pnpm add @bentley/backend-itwin-client@2.18.0-dev.15
yarn add @bentley/backend-itwin-client@2.18.0-dev.15

Runtime dependencies

Peer requirements

Optional dependencies

  • None declared

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