</>PackageGraphPackageGraph

expo-modules-core

npmv57.0.16TypeScript

The core of Expo Modules architecture

Safe to adopt

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

  • AWeight: grade A, Excellent.

    Pulls in 5 transitive packages, about 47 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-core to a project.

3
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.

47 MB
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-modules-core, 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 expo-modules-core README.

rubyFull README ↗
# Podfile

require File.join(File.dirname(`node --print "require.resolve('react-native/package.json')"`), "scripts/react_native_pods")
require File.join(File.dirname(`node --print "require.resolve('expo-modules-core/package.json')"`), "cocoapods.rb")
require File.join(File.dirname(`node --print "require.resolve('expo-modules-core/package.json')"`), "scripts/autolinking")

#  ...

target "TargetName" do
  use_unimodules!
  config = use_native_modules!
  use_react_native!(:path => config["reactNativePath"])

  # ...
Example truncated — see the full README.

expo-modules-core 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-modules-corethis page01MIT6 days ago
expo-modules-jsi01MIT1 day ago
@expo/config9.1M5MIT1 day ago
expo-file-system8.4M1MIT1 day ago
expo-font03MIT1 day ago
expo-keep-awake01MIT1 day ago

Dependencies

Declared by expo-modules-core v57.0.16. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (3)

@expo/expo-modules-macros-plugin 0.6.1expo-modules-jsi ~57.0.8invariant ^2.2.4

Peer (3)

react *react-native *react-native-worklets ^0.7.4 || ^0.8.0 || ^0.9.0 || ^0.10.0

Dev (4)

@testing-library/react-native ^13.3.0@types/invariant ^2.2.33@types/react ~19.2.0expo-module-scripts 56.0.3

Used by

Popular packages that depend on expo-modules-core.

exponpm

The Expo SDK

↓ 0/wk◈ 18 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of expo-modules-core.

invariantexpo-modules-jsi@expo/expo-module…react-nativereact-native-work…reactexpoexpo-modules-core
expo-modules-core dependencies dependents

Frequently installed together

@expo/dom-webviewnpm

A WebView specifically designed for Expo DOM components

↓ 0/wk◈ 2 dependents⚖ MITTS
reactnpm

React is a JavaScript library for building user interfaces.

↓ 152.8M/wk◈ 82 dependents⚖ MIT
react-domnpm

React package for working with the DOM.

↓ 143.7M/wk◈ 47 dependents⚖ MIT
react-nativenpm

A framework for building native apps using React

↓ 0/wk◈ 30 dependents⚖ MIT
@expo/metro-runtimenpm

Tools for making advanced Metro bundler features work

↓ 0/wk◈ 3 dependents⚖ MITTS
@ungap/structured-clonenpm

A structuredClone polyfill

↓ 75.6M/wk◈ 2 dependents⚖ ISC
@expo/confignpm

A library for interacting with the app.json

↓ 9.1M/wk◈ 5 dependents⚖ MITTS
expo-file-systemnpm

Provides access to the local file system on the device.

↓ 8.4M/wk◈ 1 dependents⚖ MITTS
@expo/config-pluginsnpm

A library for Expo config plugins

↓ 0/wk◈ 5 dependents⚖ MITTS
whatwg-url-minimumnpm

Derivative of whatwg-url without unicode handling and optimized for Expo

↓ 0/wk◈ 1 dependents⚖ MITTS
@expo/metro-confignpm

A Metro config for running React Native projects with the Metro bundler

↓ 0/wk◈ 3 dependents⚖ MITTS
@types/reactnpm

TypeScript definitions for react

↓ 0/wk◈ 71 dependents⚖ MITTS

Release history

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

Recent versions of expo-modules-core
VersionPublishedSizeLicense
57.0.16latest6 days ago31 MBMIT
58.0.0-canary-20260902-26df09e7 days ago31 MBMIT
58.0.0-canary-20260901-2164f248 days ago31 MBMIT
57.0.158 days ago31 MBMIT
55.0.269 days ago31 MBMIT
56.0.2512 days ago29 MBMIT
57.0.1414 days ago31 MBMIT
57.0.1317 days ago31 MBMIT
57.0.1220 days ago31 MBMIT
56.0.2423 days ago29 MBMIT
57.0.1126 days ago30 MBMIT
58.0.0-canary-20260812-27f94d428 days ago31 MBMIT
58.0.0-canary-20260806-8c2d0071 month ago2.2 MBMIT
56.0.231 month ago29 MBMIT
57.0.101 month ago30 MBMIT

Overview

expo-modules-core is an npm package that the core of Expo Modules architecture. 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 the core of Expo Modules architecture 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

alanhughesbrentvatnebycedricccheeverexpo-botexpoadminexponentidekudochienphilpltsapetawschurman

Keywords

expoexpo-modulesmodulesreact-nativeunimodules

Frequently asked questions

Should I use expo-modules-core?

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

How do I install expo-modules-core?

Run `npm install expo-modules-core` to add expo-modules-core to your npm project.

How many dependencies does expo-modules-core have?

expo-modules-core declares 10 direct dependencies and pulls in 5 packages in total once its runtime tree is resolved totalling about 47 MB on disk.

What license is expo-modules-core released under?

expo-modules-core is distributed under the MIT license.

How popular is expo-modules-core?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on expo-modules-core.

Is expo-modules-core still maintained?

The most recent release of expo-modules-core (v57.0.16) was published 6 days ago.

Does expo-modules-core run install scripts?

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