question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

yarn start-storybook => freeze on 95% emitting fork-ts-checker-webpack-plugin

See original GitHub issue

Describe the bug Everything is in the issue title

To Reproduce I’m on fresh new angular 10 project. I am in the setup phase preparing all the necessary tools before starting the development.

Just to mentioned that I used Storybook for two previous projects based on Web Components and I did not meet issues.

So, based on an fresh new angular 10 project:

  1. I installed storybook from the CLI command in my fresh angular project.
  2. To test the install, I ran the command below (automatically added by storybook during its setup in my package.json): npm run storybook => the besides command is yarn start-storybook -p 6006 from the package.json
  3. Everything compiled fine and the web page is opened as well in my browser… So it’s OK until then
  4. I made a change in the file stories/Button.stories.ts (also an example file added by storybook during setup). I just changed the Button label property in the Primary story. Nothing more.
  5. The start-storybook watcher detected my change and recompile as expected. And my change appeared in the browser.
  6. I made the same change, in the same file on the same property… And… the issue appeared 95% emitting fork-ts-checker-webpack-plugin
  7. The prompt is frozen and does not exit. I have to Ctrl+c to force exit.

And the issues is reproduced each time on the second build pass after a second change I made in any file after the storybook server startup. The first pass always seems to work.

I tried to disable the typescript checker as mentioned in storybook documentation in .storybook/main.js (See here):

module.exports = {
  typescript: {
    check: false,
    checkOptions: {},
  }
};

But it seems that this setup snippet is not taken into account by the build… I tried other setup from fork-ts-checker-webpack-plugin package with fork-ts-checker config files, fork-ts-checker setup in package.json to enable logging, increase memory… But nothing seems to have an effect…

Expected behavior Finish the build and refresh the storybook web page in the browser.

Screenshots idle-after-start-screenshot ==> Idle after storybook server launch

first-pass-idle-screenshot ==> First build pass OK after a first change made in a story source file sample stories/Button.stories.ts

second-pass-freeze-screenshot ==> Second build pass freezes !!! After the same change made in the same story source file sample stories/Button.stories.ts

System:

Environment Info:

  System:
    OS: Linux 3.16 Debian GNU/Linux 8 (jessie) 8 (jessie)
    CPU: (4) x64 Intel(R) Core(TM) i5 CPU       M 480  @ 2.67GHz
  Binaries:
    Node: 12.16.1 - ~/.nvm/versions/node/v12.16.1/bin/node
    Yarn: 1.22.5 - ~/.nvm/versions/node/v12.16.1/bin/yarn
    npm: 6.14.7 - ~/.nvm/versions/node/v12.16.1/bin/npm
  Browsers:
    Chrome: 84.0.4147.135
    Firefox: 60.4.0
  npmPackages:
    @storybook/addon-actions: ^6.0.20 => 6.0.20 
    @storybook/addon-essentials: ^6.0.20 => 6.0.20 
    @storybook/addon-links: ^6.0.20 => 6.0.20 
    @storybook/angular: ^6.0.20 => 6.0.20 
    @storybook/preset-typescript: ^3.0.0 => 3.0.0

Thank you all in advance for your help or your tips !

Issue Analytics

  • State:open
  • Created 3 years ago
  • Reactions:14
  • Comments:19 (2 by maintainers)

github_iconTop GitHub Comments

5reactions
PhilippeMoriercommented, Mar 25, 2021

FYI: I have this problem with WebStorm & Angular 🤔.

3reactions
nathanielgreencommented, Feb 20, 2021

I was getting the same problem after re configuring my .vimrc for use with neovim, storybook, and angular. I went through my old settings and managed to narrow down the problem.

Adding these 2 line to my .vimrc seemed to solve the issue for me:

set nobackup      " No autocreation of backup files
set nowritebackup " No autocreation of backup files
Read more comments on GitHub >

github_iconTop Results From Across the Web

yarn start-storybook => freeze on 95% emitting fork-ts-checker ...
To test the install, I ran the command below (automatically added by storybook during its setup in my package.json ): npm run storybook...
Read more >
webpack hangs at on "95% emit" / "95% emitting"
path webpack will hang with no output. Running with the --progress flag will show that it's hanging on 95% emit(ting) (suffix depending on...
Read more >
fork-ts-checker-webpack-plugin - npm
Runs typescript type checker and linter on separate process.. Latest version: 7.2.14, last published: 9 days ago.
Read more >
parsley-storybook [javascript]: Datasheet - Package Galaxy
+ yarn install --frozen-lockfile. 38. + yarn build ... Progress] 2% setup run ForkTsCheckerWebpackPlugin ... Progress] 95% emitting emit.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found