expo-modules-jsi
npmv57.1.0The JavaScript Interface for Expo Modules
Safe to adopt
Yes — expo-modules-jsi scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 1 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 1 days ago. 50 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 637 KB installed.
- 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-jsi 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.
Compatibility
- Node.js
- No constraint declared
- Module format
- CommonJS only
- TypeScript
- No bundled types
- Install scripts
- None
Quick start
A usage example from the expo-modules-jsi README.
import ExpoModulesCore
public class MyModule: Module {
public func definition() -> ModuleDefinition {
Name("MyModule")
Function("printString") { (value: JavaScriptValue) in
print(value.getString())
}
}
}expo-modules-jsi 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-jsithis page | 0 | 1 | MIT | 1 day 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/local-build-cache-provider | 0 | 1 | MIT | 1 day ago |
| babel-preset-expo | 0 | 1 | MIT | 1 day ago |
Dependencies
Declared by expo-modules-jsi v57.1.0. Runtime dependencies are installed with the package; dev dependencies are not.
Peer (1)
Used by
Popular packages that depend on expo-modules-jsi.
Relationship graph
Dependencies (left) and dependents (right) of expo-modules-jsi.
Frequently installed together
React is a JavaScript library for building user interfaces.
The React Native multithreading library
A framework for building native apps using React
Swift macro plugin for Expo modules
Simple and complete React Native testing utilities that encourage good testing practices.
invariant
TypeScript definitions for react
Release history
50 releases in the last two years, typically about 2 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 57.1.0latest | 1 day ago | 637 KB | MIT |
| 58.0.0-canary-20260908-e343e6e | 1 day ago | 647 KB | MIT |
| 57.0.8 | 6 days ago | 605 KB | MIT |
| 58.0.0-canary-20260902-26df09e | 7 days ago | 588 KB | MIT |
| 58.0.0-canary-20260901-2164f24 | 8 days ago | 588 KB | MIT |
| 57.0.7 | 8 days ago | 543 KB | MIT |
| 56.0.13 | 12 days ago | 409 KB | MIT |
| 57.0.6 | 14 days ago | 542 KB | MIT |
| 57.0.5 | 20 days ago | 540 KB | MIT |
| 58.0.0-canary-20260812-27f94d4 | 28 days ago | 571 KB | MIT |
| 58.0.0-canary-20260806-8c2d007 | 1 month ago | 571 KB | MIT |
| 57.0.0-canary-20260723-64edab9 | 1 month ago | 549 KB | MIT |
| 57.0.4 | 1 month ago | 540 KB | MIT |
| 57.0.0-canary-20260720-b6d63bc | 1 month ago | 545 KB | MIT |
| 57.0.0-canary-20260718-7cbcda5 | 1 month ago | 543 KB | MIT |
Overview
expo-modules-jsi is an npm package that the JavaScript Interface for Expo Modules. It has 1 known dependents in the graph. The latest version is 57.1.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need the JavaScript Interface for Expo Modules and value a focused solution.
When not to use it
Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.
Pros
- Clear open-source license (MIT).
- Lean dependency tree (1 direct dependencies).
Cons
- No bundled TypeScript types (may require a separate @types package).
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Frequently asked questions
Should I use expo-modules-jsi?
Yes — expo-modules-jsi scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 1 days ago. 50 releases in the last 2 years.
How do I install expo-modules-jsi?
Run `npm install expo-modules-jsi` to add expo-modules-jsi to your npm project.
What license is expo-modules-jsi released under?
expo-modules-jsi is distributed under the MIT license.
How popular is expo-modules-jsi?
npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on expo-modules-jsi.
Is expo-modules-jsi still maintained?
The most recent release of expo-modules-jsi (v57.1.0) was published 1 day ago.
Does expo-modules-jsi run install scripts?
No. expo-modules-jsi does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.