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

the '-h' option alone alias to '--host' instead of '--help' when used as CLI tool #239

Closed

Comments

@tinunkai
Copy link

@tinunkai tinunkai commented Jan 9, 2019

Issue description

The document

-V, --version output the version number
-m, --mode Analyzer mode. Should be server or static.
In server mode analyzer will start HTTP server to show bundle report.
In static mode single HTML file with bundle report will be generated. (default: server)
-h, --host Host that will be used in server mode to start HTTP server. (default: 127.0.0.1)
-p, --port Port that will be used in server mode to start HTTP server. (default: 8888)
-r, --report Path to bundle report file that will be generated in static mode. (default: report.html)
-s, --default-sizes Module sizes to show in treemap by default.
Possible values: stat, parsed, gzip (default: parsed)
-O, --no-open Don't open report in default browser automatically.
-e, --exclude Assets that should be excluded from the report.
Can be specified multiple times.
-l, --log-level Log level.
Possible values: debug, info, warn, error, silent (default: info)
-h, --help output usage information

says it has two -h options when used as CLI tool.
I think the -h alone expect alias to --help instead of --host, right?

Thanks!

Technical info

  • Webpack Bundle Analyzer version: 3.03
  • Webpack version: 4.28.1
  • Node.js version: 10.13.0
  • npm/yarn version: 6.5.0
  • OS: Manjaro Linux 18.0.1

Debug info

How do you use this module? As CLI utility or as plugin?

CLI

If CLI, what command was used? (e.g. webpack-bundle-analyzer -O path/to/stats.json)

npx webpack-bundle-analyzer -h

@th0r th0r closed this in #260 Apr 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment