Conversation
# Why - We did similar cleanup for Android in #43097 - The View with RN app was too cluttered and hard to read # How Extracted all brownfield testing code to a separate `ObservableObject` # Test Plan Verified that the test app works as previously and communication API works # Checklist - [X] 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) - [X] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin).
… and `URL` input (#43194) # Why Resolves #43193 Resolves #43192 This fixes a few discrepancies in the `expo/fetch` implementation that were reported in the linked issues and further that I noticed when double-checking the against [`fetch-nodeshim`](https://github.com/kitten/fetch-nodeshim) (which I previously checked against the Fetch standard) # How - `method` needs to be normalised to uppercase (this isn't obvious in the standard; commit links to section) - input needs to accept `URL` and stringify it - input needs to accept `Request` and replace `init` with it - **NOTE:** Typically, only one argument is used in that case, but it's more convenient to express it as a "replacement." I've added a custom `FetchRequestLike` type to mirror `RequestInit` - `body` and `signal` need to accept `null` as valid input values in `FetchRequestInit` # Test Plan - Unclear how we typically test this, but could manually verify this; changes are pretty straightforward though - For type compatibility, `fetch(new URL('...'))` and `fetch(new Request('...'))` shouldn't raise type errors # Checklist <!-- Please check the appropriate items below if they apply to your diff. --> - [x] 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)
…43211) ## Why Fix ENG-19537 ## How - Added a `UI_ONLY_FRONTMATTER_FIELDS` set in `scripts/generate-markdown-pages-utils.ts` listing the 8 fields to strip: `hideTOC`, `maxHeadingDepth`, `hideFromSearch`, `hideInSidebar`, `sidebar_title`, `searchRank`, `searchPosition`, `hasVideoLink`. - Added a second `.filter()` step in `extractFrontmatter()` that checks each YAML line's key against the set and drops matches. - Added two test cases in `scripts/generate-markdown-pages-utils.test.ts`: one verifying UI-only fields are stripped while semantic fields (`isDeprecated`, `isAlpha`) are preserved, and one verifying that frontmatter containing only UI-only fields returns `null`. - Semantic fields like `title`, `description`, `modificationDate`, `isDeprecated`, `isAlpha`, `isNew`, and `cliVersion` are preserved since they provide useful signals. ## Test Plan Run `yarn run generate-markdown-pages` then `yarn run generate-llms` - Verify that `llms-eas.txt`, `llms-full.txt`, and `llms-sdk.txt` no longer contain `hideTOC`, `maxHeadingDepth`, `sidebar_title`, `searchRank`, `searchPosition`, `hideFromSearch`, `hideInSidebar`, or `hasVideoLink` in frontmatter blocks. - Confirm that `title`, `description`, `modificationDate`, `isDeprecated`, `isAlpha`, and `isNew` are still present. <img width="1716" height="272" alt="CleanShot 2026-02-17 at 19 39 53@2x" src="https://github.com/user-attachments/assets/dcfa0a75-b147-41c7-af2a-f327a9f073c9" /> <img width="1356" height="304" alt="CleanShot 2026-02-17 at 19 40 23@2x" src="https://github.com/user-attachments/assets/66d100ac-dbcb-4bfe-9d53-fa9f7b735cbd" /> **Alternatively, you can run `yarn export` and `npx serve out`** and visit pages like "Create and use config plugins" and "Using existing credentials" and click View Markdown button on these pages. ## 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 Fix ENG-10293 Developers who build locally with `npx expo run:android` or `npx expo run:ios` often keep using those commands for every iteration, waiting a minute or more for native compilation when they only changed JavaScript code. The existing page documents the `run` commands but never explains that `npx expo start` is the faster workflow for daily development after the first build. ## How - Expand the explanation of what `run` commands do to clarify that they perform two steps: compile and install the native binary, then start Metro - Add a new `After the first build: use npx expo start` subsection with the practical workflow pattern - Add a comparison table showing when to use `run` vs `start` and what each command does. - Fix broken anchor links and link to CNG and prebuild documentation. ## Test Plan - Open the link locally: http://localhost:3002/guides/local-app-development/#after-the-first-build-use-npx-expo-start or open preview link: https://pr-43224.expo-docs.pages.dev/guides/local-app-development/#after-the-first-build-use-npx-expo-start - Confirm the new "After the first build" subsection renders correctly with the Terminal component and comparison table. Click all internal links on the page and verify none are broken or redirect-based. # 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). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
# Why The current link is broken (404) # How This link points to docs for the 2.x version of the library. The current library version (3.x) uses hooks for tap gestures which is different from the tutorial # Test Plan N/A # 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). - [x] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
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.
4 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 : )