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

BREAKING CHANGE(config): Differentiate --timing from --loglevel #455

Closed
3 tasks done
Tracked by #443
darcyclarke opened this issue Mar 18, 2022 · 0 comments · Fixed by npm/cli#5715
Closed
3 tasks done
Tracked by #443

BREAKING CHANGE(config): Differentiate --timing from --loglevel #455

darcyclarke opened this issue Mar 18, 2022 · 0 comments · Fixed by npm/cli#5715
Assignees
Labels
Milestone

Comments

@darcyclarke
Copy link
Contributor

darcyclarke commented Mar 18, 2022

  • Add docs examples for how to do --timing to see only timing logs
  • Add example for how to do --timing --silent to write timing file to do perf analysis for timing without writing to the terminal in case that affects perf
  • Example on how to set a local directory for all logs
@darcyclarke darcyclarke mentioned this issue Mar 18, 2022
32 tasks
@darcyclarke darcyclarke changed the title Differentiate --timing from --loglevel BREAKING CHANGE(config): Differentiate --timing from --loglevel Mar 23, 2022
@lukekarrys lukekarrys added this to the v9.0.0 milestone Sep 2, 2022
lukekarrys added a commit to npm/cli that referenced this issue Oct 19, 2022
BREAKING CHANGE: `timing` and `loglevel` changes
- `timing` has been removed as a value for `--loglevel`
- `--timing` will show timing information regardless of
  `--loglevel`, except when `--silent`

Closes npm/statusboard#455
Closes npm/statusboard#454
lukekarrys added a commit to npm/cli that referenced this issue Oct 19, 2022
BREAKING CHANGE: `timing` and `loglevel` changes
- `timing` has been removed as a value for `--loglevel`
- `--timing` will show timing information regardless of
  `--loglevel`, except when `--silent`

Closes npm/statusboard#455
Closes npm/statusboard#454
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants