[MelvinBot]

Explanation of Change

Bumps transitive dev dependency launch-editor 2.14.1 → 2.14.2 in package-lock.json to fix Dependabot alerts GHSA-r825-w8mm-5pxw, GHSA-587h-7wmj-h5pm, and GHSA-698v-4r3x-3vcv. The existing shell-quote 1.12.0 already meets the new ^1.10.0 requirement.

Usage: Dev tooling only, not shipped to users. It opens a source file in your editor from dev tools. It's pulled in by:

• @callstack/repack-dev-server (npm start for native dev)
• @react-native-community/cli-tools (RN CLI)
• @rsdoctor/sdk (web bundle analysis with ANALYZE_BUNDLE=true)

Change Log

v2.14.1...v2.14.2

• fix: ensure filenames passed to editors are not considered as flags (fix: ensure filenames passed to editors are not considered as flags vitejs/launch-editor#156)
• fix: check file existence after path resolution (fix: check file existence after path resolution vitejs/launch-editor#157)
• fix: reject paths containing % on windows (fix: reject paths containing % on windows vitejs/launch-editor#155)
• fix: correctly show error when the third parameter is not passed (fix: correctly show error when the third parameter is not passed vitejs/launch-editor#153)
• refactor: extract constructWindowsLaunchCommand (refactor: extract constructWindowsLaunchCommand vitejs/launch-editor#154)
• refactor: resolve file only arguments with get args (refactor: resolve file only arguments with get args vitejs/launch-editor#147)
• fix(deps): update all non-major dependencies (fix(deps): update all non-major dependencies vitejs/launch-editor#137, fix(deps): update all non-major dependencies vitejs/launch-editor#146)
• chore(deps): CI action updates

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/695627
PROPOSAL:

Tests

1. Run npm ci and confirm npm ls launch-editor shows only 2.14.2.
2. Run npm run web, confirm the app loads.
3. Run ANALYZE_BUNDLE=true npm run build, confirm the build succeeds.

➜  App (claude-updateLaunchEditor) npm ls launch-editor
new.expensify@9.5.20-0 /Users/neilmarcellini/Expensidev/App
├─┬ @callstack/repack@5.4.1
│ └─┬ @callstack/repack-dev-server@5.4.1
│   └── launch-editor@2.14.2
├─┬ @react-native-community/cli-platform-android@20.1.0
│ └─┬ @react-native-community/cli-tools@20.1.0
│   └── launch-editor@2.14.2 deduped
└─┬ @rsdoctor/rspack-plugin@1.5.18
  └─┬ @rsdoctor/sdk@1.5.18
    └── launch-editor@2.14.2 deduped

➜  App (claude-updateLaunchEditor) 

Analyze bundle output

• Verify that no errors appear in the JS console

Offline tests

N/A, dev tooling only.

QA Steps

None. Dev-only dependency, so no user-facing change (title has [No QA]).

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified any copy / text that was added to the app is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If the PR adds or modifies the UI:
  • I asked an AI agent to review the changes for accessibility issues and addressed its findings.
  • I tested with a screen reader (VoiceOver on macOS) and verified all new/changed elements are reachable with a logical focus order.
  • I verified all new/changed elements have meaningful accessible names and roles.
  • I verified state changes are announced (e.g. checked/unchecked, expanded/collapsed, selected).
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	🔄 Running since 2026-10-26T12:54:32.538156Z	6c6a760	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[melvin-bot]

@neil-marcellini @MariaHCD One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

[MariaHCD]

@neil-marcellini you'll need to give this one an approval as well. Could you also remove the TODO in the PR description? Thanks!

[melvin-bot]

npm has a package.json file and a package-lock.json file. It seems you updated one without the other, which is usually a sign of a mistake. If you are updating a package make sure that you update the version in package.json then run npm install

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[github-actions]

🚧 neil-marcellini has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #104998 with the pinned Mobile-Expensify submodule.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-ad6df9f9-858934b-d537b933c3f3c41cb219226dc0a26e436fe242c1/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-ad6df9f9-858934b-5e5e7afdbdbf649f95e457390a9826c9db56b129/index.html

Web 🕸️
https://104998.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[OSBotify]

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 9.5.24-1 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	cancelled 🔪
🍎 iOS 🍎	cancelled 🔪

[OSBotify]

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.5.24-8 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

• Android
• iOS