expo-modules-autolinking
npmv57.0.12TypeScriptScripts that autolink Expo modules.
Adopt with care
expo-modules-autolinking is usable, with caveats. Pulls in 30 transitive packages, about 7.6 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 14 days ago. 50 releases in the last 2 years.
- CWeight: grade C, Fair — worth a look.
Pulls in 30 transitive packages, about 7.6 MB installed (at least — some of the tree is still being crawled).
- ASupply chain: grade A, Excellent.
No install scripts, 12 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-modules-autolinking 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-modules-autolinking, 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-modules-autolinking 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-modules-autolinkingthis page | 0 | 3 | MIT | 14 days ago |
| expo-modules-core | 0 | 1 | MIT | 1 day 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/metro-config | 0 | 3 | MIT | 1 day ago |
Dependencies
Declared by expo-modules-autolinking v57.0.12. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (4)
Dev (2)
Used by
Popular packages that depend on expo-modules-autolinking.
Relationship graph
Dependencies (left) and dependents (right) of expo-modules-autolinking.
Frequently installed together
A framework for building native apps using React
A WebView specifically designed for Expo DOM components
A library for interacting with the app.json
A library for Expo config plugins
The Expo SDK
Expo Router is a file-based router for React Native and web applications.
A Metro config for running React Native projects with the Metro bundler
Stringify any JavaScript value.
A library to generate a fingerprint from a React Native project
TypeScript definitions for node
Error overlay for universal Expo apps.
Generated and versioned meta-package wrapping Metro
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 | 910 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 908 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 908 KB | MIT |
| 56.0.23 | 12 days ago | 839 KB | MIT |
| 57.0.12latest | 14 days ago | 854 KB | MIT |
| 55.0.27 | 15 days ago | 932 KB | MIT |
| 57.0.11 | 16 days ago | 854 KB | MIT |
| 3.0.27 | 23 days ago | 669 KB | MIT |
| 55.0.26 | 23 days ago | 931 KB | MIT |
| 56.0.22 | 23 days ago | 837 KB | MIT |
| 57.0.10 | 26 days ago | 849 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 867 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 866 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 863 KB | MIT |
| 56.0.21 | 1 month ago | 835 KB | MIT |
Overview
expo-modules-autolinking is an npm package that scripts that autolink Expo modules. It has 3 known dependents in the graph. The latest version is 57.0.12, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need scripts that autolink Expo modules 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
Frequently asked questions
Should I use expo-modules-autolinking?
expo-modules-autolinking is usable, with caveats. Pulls in 30 transitive packages, about 7.6 MB installed (at least — some of the tree is still being crawled).
How do I install expo-modules-autolinking?
Run `npm install expo-modules-autolinking` to add expo-modules-autolinking to your npm project.
How many dependencies does expo-modules-autolinking have?
expo-modules-autolinking declares 6 direct dependencies and pulls in 30 packages in total once its runtime tree is resolved totalling about 7.6 MB on disk.
What license is expo-modules-autolinking released under?
expo-modules-autolinking is distributed under the MIT license. Its dependency tree also includes: BlueOak-1.0.0, ISC, MIT.
How popular is expo-modules-autolinking?
npm does not publish download counts. Within PackageGraph's crawl, 3 known packages depend on expo-modules-autolinking.
Is expo-modules-autolinking still maintained?
The most recent release of expo-modules-autolinking (v57.0.12) was published 14 days ago.
Does expo-modules-autolinking run install scripts?
No. expo-modules-autolinking does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.