@gatsbyjs/reach-router

Gatsby's fork to modernize reach-router

@gatsbyjs/reach-router@2.0.1 was published on 2023-01-27. Its manifest declares 2 runtime dependencies and 2 peer requirements. Bundled type declarations are not declared in the inspected metadata. No Node.js engine requirement is declared in this manifest.

All @gatsbyjs/reach-router versions · Permanent reference to 2.0.1

Package specifications

Version2.0.1
License declarationMIT
Published2023-01-27T08:47:09.559Z
Node.js requirementNot declared
Type declarationsNot declared
Runtime dependency count2
Peer requirement count2
Optional dependency count0
Minified sizeMeasurement not available yet
Minified + gzipMeasurement not available yet
Unpacked distribution size120.18 KiB
Published file count7
Package typeNot declared
ES module entrydist/index.modern.mjs
Default entrydist/index.js
Side effects declarationNot declared
Direct advisories0
Resolved graph dependencies6
Repository stars12
Repository forks6

Install @gatsbyjs/reach-router 2.0.1

npm install @gatsbyjs/reach-router@2.0.1
pnpm add @gatsbyjs/reach-router@2.0.1
yarn add @gatsbyjs/reach-router@2.0.1

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