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.

build-storybook writes to STDERR even when it's successful (causes warnings with Rush.js)

See original GitHub issue

Describe the bug build-storybook writes to STDERR even when it’s successful. This causes warnings with tools like Rush.js, which monitor STDERR for content and flag the build as “successful with warnings” as a result.

To Reproduce

$ ./node_modules/.bin/build-storybook -c storybook -o dist-storybook --quiet > stdout.txt 2> stderr.txt
$ ls -l std*
-rw-r--r-- 1 Kyle Getz 197121 703 Apr 15 12:54 stderr.txt
-rw-r--r-- 1 Kyle Getz 197121   0 Apr 15 12:54 stdout.txt

Expected behavior build-storybook should be writing normal output to STDOUT.

System

Environment Info:

  System:
    OS: Windows 10 10.0.19042
    CPU: (4) x64 Intel(R) Core(TM) i7-6600U CPU @ 2.60GHz
  Binaries:
    Node: 14.15.0 - C:\Program Files\Node.js\node.EXE
    Yarn: 1.22.5 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 6.14.8 - C:\Program Files\Node.js\npm.CMD
  Browsers:
    Chrome: 89.0.4389.114
    Edge: Spartan (44.19041.906.0), Chromium (89.0.774.75)
  npmPackages:
    @storybook/addon-actions: 6.2.8 => 6.2.8
    @storybook/addon-docs: 6.2.8 => 6.2.8
    @storybook/addon-knobs: 6.2.8 => 6.2.8
    @storybook/addons: 6.2.8 => 6.2.8
    @storybook/core: 6.2.8 => 6.2.8
    @storybook/react: 6.2.8 => 6.2.8
    @storybook/theming: 6.2.8 => 6.2.8

┆Issue is synchronized with this Asana task by Unito

Issue Analytics

State:
Created 2 years ago
Reactions:6
Comments:7 (2 by maintainers)

Top GitHub Comments

3reactions

BorysShulyakcommented, Nov 8, 2021

any news on this?

3reactions

TheBitcommented, Oct 29, 2021

@kaiyoma thanx, yesterday I was also looking for a workaround and tried to play with option 2 described here (just without redirecting to a file): package.json "build": "build-storybook --quiet 2>&1" which I guess simply redirects STDERR to STDOUT. Not sure how it will work in all cases, was worrying about if it will end up in failed builds in case of errors at all, but looks like it is (I intentionally made wrong configuration in Babel config):

If I remove wrong configuration it starts to work as expected:

Though if I intentionally change Storybook configuration to get a warning (wrong order of addons) - Rush doesn’t see the warning, which is bad, but I’d better live with this for now, instead without build cache…

Top Results From Across the Web

Issues · storybookjs/storybook · GitHub

build-storybook writes to STDERR even when it's successful (causes warnings with Rush.js) bug core good first issue help wanted. #14621 opened Apr 15, ......

storybookjs/storybook (Raised $170.00) - Issuehunt

build-storybook writes to STDERR even when it's successful (causes warnings with Rush.js). Unfunded#14621created bykaiyoma.

Ignore or prevent ESLint errors from breaking the build in a ...

If you want to force ESLint to always emit warnings (that will not stop you build) instead of errors, you need to set...

React Component Library Template Tutorial - Morioh

NPM (NPM is installed when you install Node.js on your machine); Installing packages (presume you know how to add packages to a Javascript...

ChangeLog - Index of /

(bnc#612430, ITS#6570) - Delete Operations happening during the "Refresh" phase ... Update" menu entry: this makes it possible to get the translations from ......