semver-try-require 6.2.3

micro module to require or import (versions of) modules that might not be there

semver-try-require@6.2.3 was published on 2023-06-28. Its manifest declares 1 runtime dependency and 0 peer requirements. Type declarations are bundled according to the package metadata. The declared Node.js requirement is ^14||^16||>=18.

Deprecated: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.

All semver-try-require versions · Permanent reference to 6.2.3 · Latest release

Package specifications

Version6.2.3
License declarationMIT
Published2023-06-28T19:17:52.601Z
Node.js requirement^14||^16||>=18
Type declarationsBundled declarations
Runtime dependency count1
Peer requirement count0
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size11.04 KiB
Published file count7
Package typecommonjs
ES module entryNot declared
Default entrydist/try-require.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies1
Repository starsUnknown
Repository forksUnknown

Install semver-try-require 6.2.3

npm install semver-try-require@6.2.3
pnpm add semver-try-require@6.2.3
yarn add semver-try-require@6.2.3

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