Cypress test for dynamic content error handling in Page component

[mr-baraiya]

Hi!

I opened a PR to handle failed dynamic content loading safely in the Page component.

PR: webpack/webpack.js.org#8006

The change ensures that when content is a Promise and it fails, the component renders a safe fallback instead of causing runtime issues.

I tried to add a Cypress E2E test for this behavior as requested in the PR review, but the test keeps failing in CI.

I attempted several approaches:

• Checking for the fallback message
• Verifying the page container renders
• Simulating dynamic content failure

However, none of these approaches seem to trigger the failure scenario in Cypress.

Could you please clarify what scenario should be tested for this case, or how to properly simulate dynamic content failure in Cypress?

Thanks!

[aniruddhaadak80]

Hey @mr-baraiya,

This sounds like an awesome addition to the Webpack docs. Handling failed promises gracefully in dynamic imports is super important. Usually, mocking the network request in Cypress (cy.intercept) to explicitly return a 500 status code is the best way to verify the fallback UI triggers correctly.

Let me know if you make any progress or if you need another fresh set of eyes on it!