Fix (telemetry): guard __moduleInitTimes access to prevent ReferenceError by elirangoshen · Pull Request #84265 · Expensify/App

elirangoshen · 2026-03-05T10:44:43Z

Explanation of Change

index.web.tswas accessing __moduleInitTimes as a bare identifier. A bare identifier lookup throws ReferenceError: __moduleInitTimes is not defined when the ModuleInitTimingPlugin hasn't run — for example in
Storybook (which uses its own webpack config without the plugin) or when a user has a stale browser-cached runtime bundle that predates this feature.

The fix wraps the access in a typeof guard so that if the global was never injected, it safely resolves to undefined rather than crashing:

// Before — throws ReferenceError if plugin didn't run
reportModuleInitTimes(__moduleInitTimes as ..., undefined, 1);
// After — safe: undefined if plugin didn't inject the global
reportModuleInitTimes(typeof __moduleInitTimes !== 'undefined' ? __moduleInitTimes as ... : undefined, undefined, 1);
Note: typeof undeclaredVar is the one JS operation that never throws a ReferenceError, making it the correct guard here.

Fixed Issues

$#82975

Tests

Open the web app normally — verify no console errors and module init times still appear as breadcrumbs in Sentry
Open Storybook (npm run storybook) — verify no ReferenceError: __moduleInitTimes is not defined in the console
Hard-reload the page with DevTools open — verify the RAF callback runs silently if the global is missing

Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Open the web app normally — verify no console errors and module init times still appear as breadcrumbs in Sentry
Open Storybook (npm run storybook) — verify no ReferenceError: __moduleInitTimes is not defined in the console
Hard-reload the page with DevTools open — verify the RAF callback runs silently if the global is missing

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

melvin-bot · 2026-03-05T10:45:24Z

@grgia Please 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]

aimane-chnaif · 2026-03-05T10:49:16Z

src/setup/telemetry/index.web.ts

@@ -14,6 +14,7 @@ export default function (): void {
    requestAnimationFrame(() => {
        // webpack module timing path (ModuleInitTimingPlugin injected __moduleInitTimes).
        // In dev mode, keys are relative file paths; in production they are numeric IDs.
-        reportModuleInitTimes(__moduleInitTimes as Record<string, number> | undefined, undefined, 1);
+        // Use typeof guard — bare identifier throws ReferenceError if ModuleInitTimingPlugin didn't run (e.g. Storybook, stale cache)
+        reportModuleInitTimes(typeof __moduleInitTimes !== 'undefined' ? __moduleInitTimes as Record<string, number> | undefined : undefined, undefined, 1);


Please also fix native

codecov · 2026-03-05T10:54:43Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/setup/telemetry/index.web.ts	`0.00% <0.00%> (ø)`
src/setup/telemetry/index.native.ts	`0.00% <0.00%> (ø)`
... and 421 files with indirect coverage changes

aimane-chnaif · 2026-03-05T11:54:25Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and 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)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
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 a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

Android: mWeb Chrome

iOS: HybridApp

before:

Screen.Recording.2026-03-05.at.11.52.01.am.mov

after:

Screen.Recording.2026-03-05.at.11.53.40.am.mov

iOS: mWeb Safari

MacOS: Chrome / Safari

aimane-chnaif

LGTM

melvin-bot · 2026-03-05T11:54:52Z

🎯 @aimane-chnaif, thanks for reviewing and testing this PR! 🎉

An E/App issue has been created to issue payment here: #84270.

chatgpt-codex-connector · 2026-03-05T12:13:14Z

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Codex has been enabled to automatically 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".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

trjExpensify · 2026-03-05T13:37:36Z

PR doesn’t need product input as a performance PR. Unassigning and unsubscribing myself.

grgia

Added @roryabraham to final review.

OSBotify · 2026-03-05T18:54:43Z

✋ 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 · 2026-03-05T19:11:46Z

🚧 @roryabraham has triggered a test Expensify/App build. You can view the workflow run here.

github-actions · 2026-03-05T19:16:20Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #84265.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-758edfe-3658edd-f4a310d696b7416ba66b2272ab0c2cf35cbe7aad/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-758edfe-3658edd-7e1542b1fc3faf2d38f7ce01e6199dcf460b0d37/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-06T04:17:30Z

🚀 Deployed to staging by https://github.com/roryabraham in version: 9.3.32-0 🚀

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

IuliiaHerets · 2026-03-06T11:09:52Z

Hi @elirangoshen, the storybook page doesn't open for the QA team — it shows a blank page. We noticed this comment.
Please confirm whether this can be tested by QA, or if it is internal only.

elirangoshen · 2026-03-06T11:35:21Z

Hi @elirangoshen, the storybook page doesn't open for the QA team — it shows a blank page. We noticed this comment. Please confirm whether this can be tested by QA, or if it is internal only.

Hi, its internal in my opinion, what do you think @roryabraham ?

aimane-chnaif · 2026-03-06T11:38:11Z

Storybook's not been working for ages. I think we can skip that.

IuliiaHerets · 2026-03-06T12:00:10Z

@aimane-chnaif Can we check it off then?

aimane-chnaif · 2026-03-06T12:03:10Z

@aimane-chnaif Can we check it off then?

yes

OSBotify · 2026-03-06T22:46:40Z

🚀 Deployed to production by https://github.com/blimpich in version: 9.3.32-3 🚀

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

add typeguard safety

5610875

elirangoshen requested review from a team as code owners March 5, 2026 10:44

melvin-bot bot assigned elirangoshen Mar 5, 2026

melvin-bot bot requested review from grgia and trjExpensify and removed request for a team March 5, 2026 10:44

aimane-chnaif reviewed Mar 5, 2026

View reviewed changes

adding safeguard to native

681c244

elirangoshen requested a review from aimane-chnaif March 5, 2026 11:30

aimane-chnaif approved these changes Mar 5, 2026

View reviewed changes

melvin-bot bot mentioned this pull request Mar 5, 2026

[$250] Payment issue for E/App PR#84265 #84270

Closed

trjExpensify removed their request for review March 5, 2026 13:37

grgia requested a review from roryabraham March 5, 2026 16:16

grgia reviewed Mar 5, 2026

View reviewed changes

roryabraham approved these changes Mar 5, 2026

View reviewed changes

roryabraham merged commit 758edfe into Expensify:main Mar 5, 2026
31 of 32 checks passed

OSBotify mentioned this pull request Mar 6, 2026

Deploy Checklist: New Expensify 2026-03-06 #84352

Closed

92 tasks

Conversation

elirangoshen commented Mar 5, 2026

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot bot commented Mar 5, 2026

Uh oh!

aimane-chnaif Mar 5, 2026

Choose a reason for hiding this comment

Uh oh!

elirangoshen Mar 5, 2026

Choose a reason for hiding this comment

Uh oh!

codecov bot commented Mar 5, 2026 • edited by github-actions bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

aimane-chnaif commented Mar 5, 2026

Reviewer Checklist

Screenshots/Videos

Uh oh!

aimane-chnaif left a comment

Choose a reason for hiding this comment

Uh oh!

melvin-bot bot commented Mar 5, 2026

Uh oh!

chatgpt-codex-connector bot commented Mar 5, 2026

Uh oh!

trjExpensify commented Mar 5, 2026

Uh oh!

grgia left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Mar 5, 2026

Uh oh!

github-actions bot commented Mar 5, 2026

Uh oh!

github-actions bot commented Mar 5, 2026

Uh oh!

OSBotify commented Mar 6, 2026

Uh oh!

IuliiaHerets commented Mar 6, 2026

Uh oh!

elirangoshen commented Mar 6, 2026

Uh oh!

aimane-chnaif commented Mar 6, 2026

Uh oh!

IuliiaHerets commented Mar 6, 2026

Uh oh!

aimane-chnaif commented Mar 6, 2026

Uh oh!

OSBotify commented Mar 6, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

7 participants

codecov bot commented Mar 5, 2026 •

edited by github-actions bot

Loading