The localBuildProgress value is mutated during the build, which was affecting INITIAL_BUILD_PAYLOAD causing subsequent builds to think steps had already been completed. By ensuring a clean initial value each time, this issue is avoided.
I could've avoided the mutation itself, but that would've been a brittle fix prone to regression.
📦 Published PR as canary version: 1.3.1--canary.284.bf6291a.0
:sparkles: Test out this PR locally via:
```bash
npm install @chromatic-com/storybook@1.3.1--canary.284.bf6291a.0
# or
yarn add @chromatic-com/storybook@1.3.1--canary.284.bf6291a.0
```
Fixes #252
The
localBuildProgressvalue is mutated during the build, which was affectingINITIAL_BUILD_PAYLOADcausing subsequent builds to think steps had already been completed. By ensuring a clean initial value each time, this issue is avoided.I could've avoided the mutation itself, but that would've been a brittle fix prone to regression.
📦 Published PR as canary version:
1.3.1--canary.284.bf6291a.0:sparkles: Test out this PR locally via: ```bash npm install @chromatic-com/storybook@1.3.1--canary.284.bf6291a.0 # or yarn add @chromatic-com/storybook@1.3.1--canary.284.bf6291a.0 ```