babel-preset-expo
npmv57.0.11TypeScriptThe Babel preset for Expo projects
Adopt with care
babel-preset-expo is usable, with caveats. Pulls in 107 transitive packages, about 18 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 107 transitive packages, about 18 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 babel-preset-expo 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 babel-preset-expo, 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
Quick start
A usage example from the babel-preset-expo README.
[
'babel-preset-expo',
{
'react-compiler': {
sources: (filename) => {
// Match file names to include in the React Compiler.
return filename.includes('src/path/to/dir');
},
},
},
];babel-preset-expo 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 |
|---|---|---|---|---|
| babel-preset-expothis page | 0 | 1 | MIT | 1 day ago |
| jsc-safe-url | 9.8M | 2 | 0BSD | 1 day ago |
| @expo/config | 9.1M | 5 | MIT | 1 day ago |
| expo-file-system | 8.4M | 1 | MIT | 1 day ago |
| @react-native/metro-config | 4.4M | 6 | MIT | 1 day ago |
| @expo/config-plugins | 0 | 5 | MIT | 1 day ago |
Dependencies
Declared by babel-preset-expo v57.0.11. Runtime dependencies are installed with the package; dev dependencies are not.
Runtime (42)
Dev (13)
Used by
Popular packages that depend on babel-preset-expo.
Relationship graph
Dependencies (left) and dependents (right) of babel-preset-expo.
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 |
|---|---|---|---|
| 57.0.11latest | 1 day ago | 304 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 302 KB | MIT |
| 57.0.10 | 8 days ago | 304 KB | MIT |
| 56.0.20 | 12 days ago | 304 KB | MIT |
| 57.0.9 | 14 days ago | 304 KB | MIT |
| 55.0.25 | 15 days ago | 154 KB | MIT |
| 57.0.8 | 17 days ago | 304 KB | MIT |
| 57.0.7 | 26 days ago | 304 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 302 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 302 KB | MIT |
| 56.0.19 | 1 month ago | 304 KB | MIT |
| 57.0.6 | 1 month ago | 304 KB | MIT |
| 57.0.5 | 1 month ago | 299 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 297 KB | MIT |
| 56.0.18 | 1 month ago | 299 KB | MIT |
Overview
babel-preset-expo is an npm package that the Babel preset for Expo projects. It has 1 known dependents in the graph. The latest version is 57.0.11, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need the Babel preset for Expo projects 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 (59 direct dependencies) increases install size and audit surface.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use babel-preset-expo?
babel-preset-expo is usable, with caveats. Pulls in 107 transitive packages, about 18 MB installed (at least — some of the tree is still being crawled).
How do I install babel-preset-expo?
Run `npm install babel-preset-expo` to add babel-preset-expo to your npm project.
How many dependencies does babel-preset-expo have?
babel-preset-expo declares 59 direct dependencies and pulls in 107 packages in total once its runtime tree is resolved totalling about 18 MB on disk.
What license is babel-preset-expo released under?
babel-preset-expo is distributed under the MIT license. Its dependency tree also includes: Apache-2.0, CC-BY-4.0, ISC, MIT.
How popular is babel-preset-expo?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on babel-preset-expo.
Is babel-preset-expo still maintained?
The most recent release of babel-preset-expo (v57.0.11) was published 1 day ago.
Does babel-preset-expo run install scripts?
No. babel-preset-expo does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.