Running the UI demo locally with npm run start causes a 404 error

Summary

When the UI demo app is started with npm run start rather than npx next start, and you load the UI home page in the browser, it fails to render and shows a 404 error:

GET http://192.168.1.151:8080/_next/static/chunks/61e9f55f639fb035.js net::ERR_ABORTED 404 (Not Found)

Is this a new feature?

• Yes, this is a new feature
• No, this is a change to existing functionality

Description of existing functionality

Build the app. Run it with PORT=8080 npm run start. Open the home (root) page with route / in the browser.

Recommended approach or architecture

This could have been caused by the recent changes to eliminate a warning related to the standalone build parameter that is there for the containerized deployment and changing how we run the app to use npm run start instead of npx next start. It could also be related to how it's built. This 404 error happens in an uncontainerized environment after the app is built.