Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: --loglevel has no impact on output during build #22061

Open
pm0u opened this issue Apr 12, 2023 · 4 comments
Open

[Bug]: --loglevel has no impact on output during build #22061

pm0u opened this issue Apr 12, 2023 · 4 comments

Comments

@pm0u
Copy link

pm0u commented Apr 12, 2023

Describe the bug

Adding the loglevel flag:

yarn build-storybook --loglevel verbose

seems to not change the output at all, only info level is ever shown. If a random string matching no available parameters is used, no error is shown either.

To Reproduce

https://github.com/pm0u/storybook-enhanced-resolve-repro

run yarn build-storybook --loglevel verbose
run yarn build-storybook --loglevel silent
run yarn build-storybook --loglevel lskdjflkdjs

None of the above changes the output

System

Environment Info:

  System:
    OS: macOS 12.6.3
    CPU: (10) arm64 Apple M1 Max
  Binaries:
    Node: 18.15.0 - ~/.nvm/versions/node/v18.15.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v18.15.0/bin/yarn
    npm: 9.5.0 - ~/.nvm/versions/node/v18.15.0/bin/npm
  Browsers:
    Chrome: 112.0.5615.49
    Firefox: 111.0.1
    Safari: 16.3
  npmPackages:
    @storybook/addon-actions: ^7.0.4 => 7.0.4 
    @storybook/addon-essentials: ^7.0.4 => 7.0.4 
    @storybook/addon-interactions: ^7.0.4 => 7.0.4 
    @storybook/addon-links: ^7.0.4 => 7.0.4 
    @storybook/addon-mdx-gfm: ^7.0.4 => 7.0.4 
    @storybook/react: ^7.0.4 => 7.0.4 
    @storybook/react-webpack5: ^7.0.4 => 7.0.4 
    @storybook/testing-library: ^0.1.0 => 0.1.0

Additional context

No response

@pm0u
Copy link
Author

pm0u commented Apr 13, 2023

verbose:

yarn run v1.22.19
$ storybook build --loglevel verbose
@storybook/cli v7.0.4

info => Cleaning outputDir: /storybook-static
info => Loading presets
info => Building manager..
info => Manager built (84 ms)
info => Compiling preview..
info => Copying static files: /Users/pmourer/Git/_bug-repro/test-storybook/node_modules/@storybook/manager/static at /Users/pmourer/Git/_bug-repro/test-storybook/storybook-static/sb-common-assets
info Addon-docs: using MDX2
info => Using implicit CSS loaders
WARN Storybook support for Create React App is now a separate preset.
WARN To use the new preset, install `@storybook/preset-create-react-app` and add it to the list of `addons` in your `.storybook/main.js` config file.
WARN The built-in preset has been disabled in Storybook 6.0.
info => Using default Webpack5 setup
info => Preview built (7.77 s)
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
WARN This can impact web performance.
WARN Assets: 
WARN   463.c6afb563.iframe.bundle.js (583 KiB)
WARN   582.6a277f93.iframe.bundle.js (680 KiB)
WARN   153.70e7c8ef.iframe.bundle.js (407 KiB)
WARN   158.d9fe4cee.iframe.bundle.js (728 KiB)
WARN entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
WARN Entrypoints:
WARN   main (742 KiB)
WARN       runtime~main.5dd27e53.iframe.bundle.js
WARN       158.d9fe4cee.iframe.bundle.js
WARN       main.bea2db0b.iframe.bundle.js
WARN 
info => Output directory: /Users/pmourer/Git/_bug-repro/test-storybook/storybook-static
✨  Done in 10.65s.

silent:

yarn run v1.22.19
$ storybook build --loglevel silent
@storybook/cli v7.0.4

info => Cleaning outputDir: /storybook-static
info => Loading presets
info => Building manager..
info => Manager built (82 ms)
info => Compiling preview..
info => Copying static files: /Users/pmourer/Git/_bug-repro/test-storybook/node_modules/@storybook/manager/static at /Users/pmourer/Git/_bug-repro/test-storybook/storybook-static/sb-common-assets
info Addon-docs: using MDX2
info => Using implicit CSS loaders
WARN Storybook support for Create React App is now a separate preset.
WARN To use the new preset, install `@storybook/preset-create-react-app` and add it to the list of `addons` in your `.storybook/main.js` config file.
WARN The built-in preset has been disabled in Storybook 6.0.
info => Using default Webpack5 setup
info => Preview built (7.83 s)
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN Critical dependency: require function is used in a way in which dependencies cannot be statically extracted
WARN asset size limit: The following asset(s) exceed the recommended size limit (244 KiB).
WARN This can impact web performance.
WARN Assets: 
WARN   463.c6afb563.iframe.bundle.js (583 KiB)
WARN   582.6a277f93.iframe.bundle.js (680 KiB)
WARN   153.70e7c8ef.iframe.bundle.js (407 KiB)
WARN   158.d9fe4cee.iframe.bundle.js (728 KiB)
WARN entrypoint size limit: The following entrypoint(s) combined asset size exceeds the recommended limit (244 KiB). This can impact web performance.
WARN Entrypoints:
WARN   main (742 KiB)
WARN       runtime~main.5dd27e53.iframe.bundle.js
WARN       158.d9fe4cee.iframe.bundle.js
WARN       main.bea2db0b.iframe.bundle.js
WARN 
info => Output directory: /Users/pmourer/Git/_bug-repro/test-storybook/storybook-static
✨  Done in 10.74s.

@twhite96
Copy link

twhite96 commented May 3, 2023

Hmmmm. Looks like this is still an issue since 2021.
#17081

I'm not sure where the logging output is suppose to go and what is supposed to be contained in those logs but I'd like to pick this up.

@Katerina198b
Copy link

Any updates? I have same issue

@dmitrc
Copy link

dmitrc commented Feb 23, 2024

This is still an issue in 2024.
Have there been any updates on this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants