expo-asset
npmv57.0.16TypeScriptAn Expo universal module to download assets and pass them into other APIs
Adopt with care
expo-asset is usable, with caveats. Pulls in 34 transitive packages, about 8.2 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 8 days ago. 50 releases in the last 2 years.
- CWeight: grade C, Fair — worth a look.
Pulls in 34 transitive packages, about 8.2 MB 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-asset 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.
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
Every license you inherit by installing expo-asset, 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-asset 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-assetthis page | 0 | 1 | MIT | 8 days ago |
| @expo/config | 9.1M | 5 | MIT | 1 day ago |
| expo-file-system | 8.4M | 1 | MIT | 1 day ago |
| expo-font | 0 | 3 | MIT | 1 day ago |
| expo-keep-awake | 0 | 1 | MIT | 1 day ago |
| expo-constants | 0 | 6 | MIT | 1 day ago |
Dependencies
Declared by expo-asset v57.0.16. Runtime dependencies are installed with the package; dev dependencies are not.
Peer (3)
Dev (6)
Used by
Popular packages that depend on expo-asset.
Relationship graph
Dependencies (left) and dependents (right) of expo-asset.
Frequently installed together
A WebView specifically designed for Expo DOM components
React is a JavaScript library for building user interfaces.
React package for working with the DOM.
A framework for building native apps using React
Tools for making advanced Metro bundler features work
A structuredClone polyfill
A library for interacting with the app.json
Provides access to the local file system on the device.
Derivative of whatwg-url without unicode handling and optimized for Expo
A Metro config for running React Native projects with the Metro bundler
The core of Expo Modules architecture
TypeScript definitions for react
Release history
50 releases in the last two years, typically about 2 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 58.0.0-canary-20260902-26df09e | 7 days ago | 220 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 220 KB | MIT |
| 57.0.16latest | 8 days ago | 252 KB | MIT |
| 56.0.24 | 12 days ago | 252 KB | MIT |
| 57.0.15 | 14 days ago | 252 KB | MIT |
| 55.0.20 | 15 days ago | 237 KB | MIT |
| 57.0.14 | 17 days ago | 252 KB | MIT |
| 57.0.13 | 20 days ago | 252 KB | MIT |
| 55.0.19 | 23 days ago | 236 KB | MIT |
| 56.0.23 | 23 days ago | 251 KB | MIT |
| 57.0.12 | 23 days ago | 252 KB | MIT |
| 57.0.11 | 26 days ago | 252 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 220 KB | MIT |
| 57.0.10 | 1 month ago | 252 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 220 KB | MIT |
Overview
expo-asset is an npm package that an Expo universal module to download assets and pass them into other APIs. It has 1 known dependents in the graph. The latest version is 57.0.16, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need an Expo universal module to download assets and pass them into other APIs 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-asset?
expo-asset is usable, with caveats. Pulls in 34 transitive packages, about 8.2 MB installed (at least — some of the tree is still being crawled).
How do I install expo-asset?
Run `npm install expo-asset` to add expo-asset to your npm project.
How many dependencies does expo-asset have?
expo-asset declares 11 direct dependencies and pulls in 34 packages in total once its runtime tree is resolved totalling about 8.2 MB on disk.
What license is expo-asset released under?
expo-asset is distributed under the MIT license. Its dependency tree also includes: BlueOak-1.0.0, ISC, MIT.
How popular is expo-asset?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on expo-asset.
Is expo-asset still maintained?
The most recent release of expo-asset (v57.0.16) was published 8 days ago.
Does expo-asset run install scripts?
No. expo-asset does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.