Repository navigation
chore: replace expo-module-scripts with direct tooling - #335
Merged
Merged
Conversation
hassankhan
changed the title
expo-module-scripts with direct tooling
kitten
approved these changes
Oct 19, 2026
expo-module-scripts stops at 56.x on npm and its successor is private to expo/expo. The packages only used it for tsc, jest and eslint. Shared tsconfig.base.json, jest.config.base.js and eslintrc.base.js now live at the root and packages reference them. Package scripts call tsc, eslint, jest and rm -rf build directly. Tests run through @swc/jest, as in expo/expo. Lint stays on ESLint 8 with universe for now; the oxlint move is a separate change. Also drops the expo-module-scripts catalog entry and the babel-preset-expo package extension, adds the missing jest.config.js to react-native-adjust, and makes the plugin generator copy jest and eslint configs from the template.
hassankhan
force-pushed
the
@hassankhan/chore/replace-expo-module-scripts
branch
from
October 19, 2026 15:35
bd46485 to
d4cc491
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
expo-module-scriptsstops at 56.x on npm and its replacement is private toexpo/expo. Nothing here needs it beyondtsc,jestandeslint.How
tsconfig.base.json,jest.config.base.jsandeslintrc.base.jsat the root; packages reference them.tsc,eslint src,jestandrm -rf builddirectly.@swc/jest, as expo/expo does. Lint stays on ESLint 8 and universe for now; oxlint follows in a separate PR.expo-module-scriptscatalog entry and thebabel-preset-expopackage extension.Test Plan
Build, lint and tests pass for all packages. Build output is identical to the previous config for three packages checked. Lockfile shrinks by about 800 lines.