</>PackageGraphPackageGraph

expo-router

npmv57.0.20TypeScript

Expo Router is a file-based router for React Native and web applications.

Adopt with care

expo-router is usable, with caveats. Pulls in 80 transitive packages, about 21 MB installed (at least — some of the tree is still being crawled).

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • AMaintenance: grade A, Excellent.

    Last published 1 days ago. 50 releases in the last 2 years.

  • DWeight: grade D, Poor — a real concern.

    Pulls in 80 transitive packages, about 21 MB installed (at least — some of the tree is still being crawled).

  • ASupply chain: grade A, Excellent.

    No install scripts, 13 maintainers, and a contained dependency surface.

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding expo-router to a project.

27
Direct dependencies

Runtime packages this one declares itself.

80
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

21 MB
Install size

Unpacked size of this package plus its entire runtime tree.

5
Tree depth

Longest resolved dependency chain below this package.

Part of this dependency tree has not been crawled yet, so these figures are a lower bound rather than a final total.

Licenses in the dependency tree

(MIT OR CC0-1.0)MITMIT AND Apache-2.0

Every license you inherit by installing expo-router, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
No constraint declared
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

expo-router vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
expo-routerthis page02MIT1 day ago
@expo/config9.1M5MIT1 day ago
expo-file-system8.4M1MIT1 day ago
expo-font03MIT1 day ago
expo-keep-awake01MIT1 day ago
expo-constants06MIT1 day ago

Dependencies

Declared by expo-router v57.0.20. Runtime dependencies are installed with the package; dev dependencies are not.

Used by

Popular packages that depend on expo-router.

Relationship graph

Dependencies (left) and dependents (right) of expo-router.

Frequently installed together

Release history

50 releases in the last two years, typically about 2 days apart.

Recent versions of expo-router
VersionPublishedSizeLicense
57.0.20latest1 day ago5.9 MBMIT
58.0.0-canary-20260908-e343e6e1 day ago3.5 MBMIT
57.0.195 days ago5.9 MBMIT
58.0.0-canary-20260902-26df09e7 days ago3.6 MBMIT
58.0.0-canary-20260901-2164f248 days ago3.6 MBMIT
57.0.188 days ago5.9 MBMIT
56.2.2012 days ago5.9 MBMIT
57.0.1714 days ago5.9 MBMIT
57.0.1616 days ago5.9 MBMIT
57.0.1520 days ago5.9 MBMIT
55.0.1823 days ago2.9 MBMIT
56.2.1923 days ago5.9 MBMIT
57.0.1423 days ago5.9 MBMIT
57.0.1326 days ago5.9 MBMIT
58.0.0-canary-20260812-27f94d428 days ago3.8 MBMIT

Overview

expo-router is an npm package that expo Router is a file-based router for React Native and web applications. It has 2 known dependents in the graph. The latest version is 57.0.20, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need expo Router is a file-based router for React Native and web applications and value a focused solution.

When not to use it

Consider an alternative if you need to minimize your dependency tree, or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).

Cons

  • Large dependency tree (66 direct dependencies) increases install size and audit surface.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

Keywords

Frequently asked questions

Should I use expo-router?

expo-router is usable, with caveats. Pulls in 80 transitive packages, about 21 MB installed (at least — some of the tree is still being crawled).

How do I install expo-router?

Run `npm install expo-router` to add expo-router to your npm project.

How many dependencies does expo-router have?

expo-router declares 66 direct dependencies and pulls in 80 packages in total once its runtime tree is resolved totalling about 21 MB on disk.

What license is expo-router released under?

expo-router is distributed under the MIT license. Its dependency tree also includes: (MIT OR CC0-1.0), MIT, MIT AND Apache-2.0.

How popular is expo-router?

npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on expo-router.

Is expo-router still maintained?

The most recent release of expo-router (v57.0.20) was published 1 day ago.

Does expo-router run install scripts?

No. expo-router does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.