</>PackageGraphPackageGraph

expo-constants

npmv57.0.17TypeScript

Provides system information that remains constant throughout the lifetime of your app.

Safe to adopt

Yes — expo-constants scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 8 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 8 days ago. 50 releases in the last 2 years.

  • AWeight: grade A, Excellent.

    Pulls in 5 transitive packages, about 277 KB installed (at least — some of the tree is still being crawled).

  • ASupply chain: grade A, Excellent.

    No install scripts, 16 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-constants to a project.

1
Direct dependencies

Runtime packages this one declares itself.

5
Total installed

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

277 KB
Install size

Unpacked size of this package plus its entire runtime tree.

3
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

Every license you inherit by installing expo-constants, 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-constants 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-constantsthis page06MIT8 days ago
@expo/config9.1M5MIT1 day ago
expo-file-system8.4M1MIT1 day ago
@expo/dom-webview02MIT1 day ago
@expo/local-build-cache-provider01MIT1 day ago
babel-preset-expo01MIT1 day ago

Dependencies

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

Runtime (1)

Dev (5)

@types/node ^22.14.0expo 57.0.19expo-manifests 57.0.1expo-module-scripts 56.0.3expo-updates 57.0.20

Used by

Popular packages that depend on expo-constants.

Relationship graph

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

Frequently installed together

Release history

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

Recent versions of expo-constants
VersionPublishedSizeLicense
58.0.0-canary-20260902-26df09e7 days ago105 KBMIT
58.0.0-canary-20260901-2164f248 days ago105 KBMIT
57.0.17latest8 days ago133 KBMIT
57.0.1612 days ago133 KBMIT
56.0.2512 days ago132 KBMIT
57.0.1514 days ago133 KBMIT
57.0.1417 days ago133 KBMIT
57.0.1320 days ago133 KBMIT
18.0.1423 days ago126 KBMIT
56.0.2423 days ago132 KBMIT
57.0.1223 days ago133 KBMIT
57.0.1126 days ago133 KBMIT
58.0.0-canary-20260812-27f94d428 days ago104 KBMIT
57.0.101 month ago133 KBMIT
58.0.0-canary-20260806-8c2d0071 month ago104 KBMIT

Overview

expo-constants is an npm package that provides system information that remains constant throughout the lifetime of your app. It has 6 known dependents in the graph. The latest version is 57.0.17, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need provides system information that remains constant throughout the lifetime of your app 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-constants?

Yes — expo-constants scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 8 days ago. 50 releases in the last 2 years.

How do I install expo-constants?

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

How many dependencies does expo-constants have?

expo-constants declares 8 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 277 KB on disk.

What license is expo-constants released under?

expo-constants is distributed under the MIT license.

How popular is expo-constants?

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

Is expo-constants still maintained?

The most recent release of expo-constants (v57.0.17) was published 8 days ago.

Does expo-constants run install scripts?

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