storybookjs/storybook

[Bug]: Revert workaround for webpack lazy compilation bug

Open

#32302 opened on Aug 20, 2025

View on GitHub
 (1 comment) (1 reaction) (0 assignees)TypeScript (89,909 stars) (10,058 forks)batch import
bughelp wanted

Description

Describe the bug

Webpack has now fixed the lazy compilation bug that prompted us to add a workaround in #18432. Confirmed both reproductions are resolved.

In the Storybook repro, the test runner still times out on the first run, but that seems unrelated to the webpack bug (and likely already addressed elsewhere). Since the test runner already warns users about lazy compilation, reverting this workaround shouldn’t make things worse.

We should

  • Remove the work
  • Verify Storybook still runs correctly with lazy compilation enabled
  • Confirm test runner behavior remains consistent

Reproduction link

https://github.com/webpack/webpack/issues/15541

Reproduction steps

No response

System

-

Additional context

No response

Contributor guide

Tech stack
typescriptjavascript
Domain
frontendtesting
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review PR #18432 to identify the workaround files (likely in the webpack config). Revert those changes, then run Storybook with lazy compilation enabled to verify it works. Also run the test runner to ensure no regression. Check the linked webpack issue for context.