expo-server
npmv57.0.3TypeScriptServer API for Expo Router projects
Safe to adopt
Yes — expo-server scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 26 days ago. 50 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 26 days ago. 50 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 361 KB installed.
- 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-server to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
Longest resolved dependency chain below this package.
Compatibility
- Node.js
- node >=20.16.0
- Module format
- ESM + CommonJS
- TypeScript
- Types included
- Install scripts
- None
expo-server vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| expo-serverthis page | 0 | 3 | MIT | 26 days ago |
| @expo/config | 9.1M | 5 | MIT | 1 day ago |
| expo-file-system | 8.4M | 1 | MIT | 1 day ago |
| @expo/devtools | 0 | 1 | MIT | 1 day ago |
| expo-modules-core | 0 | 1 | MIT | 1 day ago |
| @expo/metro-config | 0 | 3 | MIT | 1 day ago |
Dependencies
Declared by expo-server v57.0.3. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (5)
Used by
Popular packages that depend on expo-server.
Relationship graph
Dependencies (left) and dependents (right) of expo-server.
Frequently installed together
The Expo SDK
Expo Router is a file-based router for React Native and web applications.
Error overlay for universal Expo apps.
React Server Components bindings for DOM using Webpack. This is intended to be integrated into meta-frameworks. It is not intended to be imported directly.
Native navigation primitives for your React Native app.
TypeScript definitions for node
TypeScript definitions for debug
Lightweight debugging utility for Node.js and the browser
Tools for making advanced Metro bundler features work
Reusable JSON Schema (Draft 04) validation library for Expo
A framework for building native apps using React
No description provided.
Release history
50 releases in the last two years, typically about 2 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 58.0.0-canary-20260908-e343e6e | 1 day ago | 319 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 319 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 319 KB | MIT |
| 55.0.12 | 23 days ago | 328 KB | MIT |
| 56.0.6 | 23 days ago | 360 KB | MIT |
| 57.0.3latest | 26 days ago | 361 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 319 KB | MIT |
| 57.0.2 | 1 month ago | 361 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 315 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 313 KB | MIT |
| 57.0.0-canary-20260720-b6d63bc | 1 month ago | 313 KB | MIT |
| 57.0.0-canary-20260718-7cbcda5 | 1 month ago | 313 KB | MIT |
| 57.0.0-canary-20260716-381e806 | 1 month ago | 313 KB | MIT |
| 57.0.1 | 1 month ago | 356 KB | MIT |
| 56.0.5-canary-20260701-9100865 | 2 months ago | 305 KB | MIT |
Overview
expo-server is an npm package that server API for Expo Router projects. It has 3 known dependents in the graph. The latest version is 57.0.3, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need server API for Expo Router projects and value a focused solution.
When not to use it
Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.
Pros
- Ships TypeScript type definitions.
- Clear open-source license (MIT).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Keywords
Frequently asked questions
Should I use expo-server?
Yes — expo-server scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 26 days ago. 50 releases in the last 2 years.
How do I install expo-server?
Run `npm install expo-server` to add expo-server to your npm project.
What license is expo-server released under?
expo-server is distributed under the MIT license.
How popular is expo-server?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on expo-server.
Is expo-server still maintained?
The most recent release of expo-server (v57.0.3) was published 26 days ago.
Does expo-server run install scripts?
No. expo-server does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.