@azure/ms-rest-azure-env 1.1.1

Isomorphic library that provides Azure endpoints for different Azure Environments/Clouds.

@azure/ms-rest-azure-env@1.1.1 was published on 2018-11-29. Its manifest declares 0 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 been deprecated. new Azure Management SDK package from [Azure SDK for JavaScript](https://github.com/azure/azure-sdk-for-js) now have the cloud settings built-in, [for example](https://github.com/Azure/azure-sdk-for-js/blob/dc5f9743b05ea78f938eba31cbe704150889490c/sdk/sql/arm-sql/src/static-helpers/cloudSettingHelpers.ts).

All @azure/ms-rest-azure-env versions · Permanent reference to 1.1.1 · Latest release

Package specifications

Version1.1.1
License declarationMIT
Published2018-11-29T22:10:31.874Z
Node.js requirementNot declared
Type declarationsBundled declarations
Runtime dependency count0
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size73.02 KiB
Published file count13
Package typeNot declared
ES module entry./es/lib/azureEnvironment.js
Default entry./dist/msRestAzureEnv.js
Side effects declarationfalse
Direct advisoriesUnknown
Resolved graph dependenciesUnknown
Repository starsUnknown
Repository forksUnknown

Install @azure/ms-rest-azure-env 1.1.1

npm install @azure/ms-rest-azure-env@1.1.1
pnpm add @azure/ms-rest-azure-env@1.1.1
yarn add @azure/ms-rest-azure-env@1.1.1

Runtime dependencies

  • None declared

Peer requirements

  • None declared

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