[Due for payment 2025-10-21] Fix the web production build locally not working

@abekkala

Coming from https://expensify.slack.com/archives/C08CZDJFJ77/p1749629334304079

Using the npm run web:prod seems to not work reliably and the app runs into the 404 issues. Let's make sure this flow works and developers can run and test the production web build

Issue Owner

Current Issue Owner: @abekkala

@Pujan92

Triggered auto assignment to Contributor-plus team member for initial proposal review - @Pujan92 (External)

@abekkala

Triggered auto assignment to @abekkala (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

Proposal

Please re-state the problem that we are trying to solve in this issue.

Fix the web production build locally not working

What is the root cause of that problem?

Improvement

What changes do you think we should make in order to solve the problem?

We need replace http-server with serve here in order to avoid 404 issues

App/package.json

Line 79 in 25a9740

"web:prod": "http-server ./dist --cors",

 "web:prod": "npx serve ./dist --cors",

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

n/A

What alternative solutions did you explore? (Optional)

n/A

Reminder: Please use plain English, be brief and avoid jargon. Feel free to use images, charts or pseudo-code if necessary. Do not post large multi-line diffs or write walls of text. Do not create PRs unless you have been hired for this job.

@PiyushChandra17

Currently, the README instructions for production build is:

#### Local production build of the web app
In order to generate a production web build, run `npm run build`, this will generate a production javascript build in the `dist/` folder.

Standard development builds are run with npm run web. For production builds, there is an additional script: npm run web:prod. We can assume that this is proper way to build and run locally production web:

npm run build
npm run web:prod

This successfully starts the local production website, but API requests return a CORS errors or 404 errors (depends on USE_WEB_PROXY env flag). There are likely additional steps required to make it work, possibly including changes to environment files that should be documented in the README or additional proxy commend.

@PiyushChandra17 I tried your solution but it didn’t work. Could you check if there are any additional settings in the environment files? Is there any command that should be run besides these two?

with USE_WEB_PROXY true:

@LukasMod

@LukasMod In the env prod, we can set USE_WEB_PROXY ENV flag to true here

App/.env.production

Line 7 in ba30be5

USE_WEB_PROXY=false

And -P additional proxy flag

"web:prod": "http-server ./dist --cors -P http://localhost:8080?"

@PiyushChandra17

@PiyushChandra17 I did try with that proposition "web:prod": "http-server ./dist --cors -P http://localhost:8080?" and USE_WEB_PROXY set to true in env.production, but got loop with wrong requests in terminal and still offline indicator in web (there is no 404 requests, but it seems not right in terminal for sure).

"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36"
[2025-09-04T12:49:49.048Z]  "POST ?/(..)/?/?/?/?/?/?/?/?/?/?/?/?/?/api/SendPerformanceTiming?"

On your side, are you able to interact or log in normally after running that command? I wonder if there’s something else that needs to be configured to make this work.

@LukasMod

@LukasMod This is exactly what's happening

USE_WEB_PROXY=true - > the app expects the local dev proxy to forward API calls, this kinda works with npm run web but not with npm run web:prod
USE_WEB_PROXY=false - > the app calls the prod API directly - > which leads to CORS/404 restrictions

So just running

npm run build
npm run web:prod
this isn't enough

We need:

Proper proxy set up for prod builds so the local server rewrites API BE
Or correct .env overrides so the app points to the correct working production level BE without trigerring CORS issues

We need to start the proxy server too along with those two commands

App/package.json

Line 30 in ba30be5

"web-proxy": "ts-node web/proxy.ts",

Set the USE_WEB_PROXY=true in .env prod
Update the web:prod npm script if needed (just working on this and let's see what resolves the issue)
Run web-proxy

npm run build
npm run web:prod
npm run web-proxy

Reviewing label has been removed, please complete the "BugZero Checklist".

@Pujan92

The solution for this issue has been 🚀 deployed to production 🚀 in version 9.2.30-6 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

[No-QA] fix: the web production build locally not working #71958

If no regressions arise, payment will be issued on 2025-10-21. 🎊

For reference, here are some details about the assignees on this issue:

@Pujan92 requires payment through NewDot Manual Requests
@TaduJR requires payment (Needs manual offer from BZ)

@Pujan92

@Pujan92 @abekkala The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the BugZero Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]

@TaduJR

PAYMENT SUMMARY FOR OCT 21

Fix: @TaduJR [$250, if no regressions] payment via Upwork OFFER
PR Review: @Pujan92 [$250, if no regressions] payment via NewDot
please complete checklist above - thanks!

@abekkala

@abekkala no need for the checklist here.

@Pujan92

Thank you @Pujan92

@TaduJR

Fix: @TaduJR payment sent via Upwork and contract ended!
PR Review: @Pujan92 [$250] payment via NewDot

THANKS! 🎉

@Pujan92

$250 approved for @Pujan92

Navigation Menu

Repository navigation

[Due for payment 2025-10-21] Fix the web production build locally not working #69854

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

56 remaining items

PAYMENT SUMMARY FOR OCT 21

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[Due for payment 2025-10-21] Fix the web production build locally not working #69854

Description

Activity

melvin-bot commented on Sep 4, 2025

melvin-bot commented on Sep 4, 2025

PiyushChandra17 commented on Sep 4, 2025

Proposal

Please re-state the problem that we are trying to solve in this issue.

What is the root cause of that problem?

What changes do you think we should make in order to solve the problem?

What specific scenarios should we cover in automated tests to prevent reintroducing this issue in the future?

What alternative solutions did you explore? (Optional)

LukasMod commented on Sep 4, 2025

PiyushChandra17 commented on Sep 4, 2025

LukasMod commented on Sep 4, 2025

PiyushChandra17 commented on Sep 4, 2025

PiyushChandra17 commented on Sep 4, 2025

56 remaining items

melvin-bot commented on Oct 14, 2025

melvin-bot commented on Oct 14, 2025

melvin-bot commented on Oct 14, 2025

abekkala commented on Oct 16, 2025

PAYMENT SUMMARY FOR OCT 21

Pujan92 commented on Oct 16, 2025

abekkala commented on Oct 17, 2025

abekkala commented on Oct 21, 2025

JmillsExpensify commented on Oct 22, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions