Closed valentinpalkovic closed 8 months ago
Thanks for raising the issue; we've been able to reproduce the problem by following your instructions.
While we investigate the cause, you may pause Console Ninja on your project when you start storybook as a short term workaround.
We have found the cause of your problem and fixed it in the latest version of Console Ninja, v1.0.289
.
Console Ninja was attempting to process .yarn
folder dependencies, and this resulted in a slow startup time for this sample project. Console Ninja now ignores files in the .yarn
folder.
What happened?
I found out that
Console Ninja
in its latest version somehow affects Storybook's startup time by a lot. Normally the manager starts up in approx. 500ms. Now it takes almost 3 minutes for Storybook to start.Debugging showed me, that
esbuild
related functions.Version
1.0.288 (1.0.287 is not affected)
Steps to reproduce (or sample repo)
nextjs/default-ts/after-storybook
npm install
npm run storybook
-> Storybook takes 3 minutes to start (normally it takes like 500ms)Log output