Conversation
# Why VS Code search results in this monorepo include build artifacts (`packages/**/build`) and generated docs data (`docs/public/static/data`), adding noise when searching for code. # How Added `search.exclude` entries to `.vscode/settings.json` to omit these directories from search results. # Test Plan Open the repo in VS Code and confirm that searching no longer returns results from `packages/**/build` or `docs/public/static/data`. # Checklist - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
# Why <!-- Please describe the motivation for this PR, and link to relevant GitHub issues, forums posts, or feature requests. --> Bump EAS CLI version in doc's metadata. # How <!-- How did you build this feature or fix this bug and why? --> Run `yarn run eas-cli-sync`. # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
…ion` (#43292) # Why The `experiments.autolinkingModuleResolution` option will be auto-enabled for monorepos in SDK 55. It's also not considered "alpha-quality" any longer, and the `experiments` flag is sufficient to communicate that it's (usually) not the default, and we shouldn't warn people that it's an early preview anymore. This is safe to enable regardless of whether apps are on SDK 54 or 55, and we'll backport any fixes (no fixes had to be backported so far) # How - Remove alpha callouts for `autolinkingModuleResolution` - Add notes that the option is enabled for monorepos by default
#43182) # Why Extracts link preview adapter logic - synthesizing react-navigation state during link preview transition - from native stack fork into a separate hook in order to simplify the code and make it testable. # How 1. Extract the logic from native stack to `usePreviewTransition` 2. Changes the way formsheet header overrides are applied - changes are applied to the spread object # Test Plan 1. Unit tests 2. Manual testing of link preview, zoom transition with gestures disabled and formsheets headers **Link preview and zoom transitions** - `yarn ios:link-preview` https://github.com/user-attachments/assets/35709f9d-366d-49e8-a554-3e6a7f1c5207 **Formsheet headers** - `yarn ios:native-navigation` Header is transparent by default <img height="512" alt="Simulator Screenshot - iPhone 17 Pro - 2026-02-17 at 11 02 50" src="https://github.com/user-attachments/assets/65c2a10d-6402-4d54-b27e-a843a407626e" /> # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
#43200) # Why When writing code in `expo-router` Claude tends to use `useContext` instead of `use`, and hardly ever uses React 19 features. Additionally it often tries to use `any` to fix the types # How <!-- How did you build this feature or fix this bug and why? --> # Test Plan <!-- Please describe how you tested this change and how a reviewer could reproduce your test, especially if this PR does not include automated tests! If possible, please also provide terminal output and/or screenshots demonstrating your test/reproduction. --> # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [ ] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
## Why Following up on the discussion in [#42797](#42797), this PR adds a known limitation entry for the noticeable latency users experience when opening or dismissing screens that use zoom transitions. Users report a delay of approximately 1 second, especially when performing rapid open/close/open gestures. This delay feels significantly higher than the default push transition or native iOS apps using the same zoom transition API. The issue is upstream in `react-native-screens` related to how it handles transitions on iOS 18+, and expo-router cannot fix it directly. ## How - Added a new collapsible entry to "Known limitations" section in the zoom transition documentation page. - The warning describes the delay, clarifies that this is an upstream `react-native-screens` issue (not an expo-router bug), notes that the Expo team is actively working with the `react-native-screens` team to improve this, and links to the tracking issue for updates. ## Test Plan Add the collapsible and verify it renders correctly using the docs Next.js dev server. ## Checklist - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) --------- Co-authored-by: Aman Mittal <amandeepmittal@live.com> Co-authored-by: Jakub Tkacz <32908614+Ubax@users.noreply.github.com>
# Why This adds support for a `EXPO_NO_QR_CODE` env variable to allow skipping printing the QR code on screen. I've tried with `CI=1` but it also suppresses a bit of the interactivity which I'd like to retain. Ideally if I could provide my own QR code content, that would be gold, but feels a bit too specific to my use case. Instead I'd rather print my QR code on console first, and then let `expo start` run afterwards without QR code. # Test Plan Please let me know how to test this. # Checklist <!-- Please check the appropriate items below if they apply to your diff. This is required for changes to Expo modules. --> - [ ] Documentation is up to date to reflect these changes (eg: https://docs.expo.dev and README.md). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )