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

chore(webpack-cli): remove pretty output functionality #1316

Merged

Conversation

ematipico
Copy link
Contributor

What kind of change does this PR introduce?

I kind of breaking change but it's needed for webpack ecosystem.

Did you add tests for your changes?
I removed the tests that are not needed

If relevant, did you update the documentation?
Yes

Summary
This PR removes --pretty argument and all the code behind it. Also, it removes cli-table3 which is not maintained anymore (it still runs on node 6 and there are no updates on future releases).

Does this PR introduce a breaking change?

It could, but I don't the --pretty argument was used so much. An alternative will be available inside webpack core

Other information

@ematipico ematipico requested a review from a team as a code owner March 11, 2020 12:24
@@ -14,7 +14,7 @@ class StatsGroup extends GroupHelper {

resolveOptions() {
if (this.args.verbose && this.args.stats) {
logger.warn('Conflict between "verbose" and "stats" options. Using verbose.');
logger.warn('Conflict between "verbqose" and "stats" options. Using verbose.');
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo?

@ematipico ematipico force-pushed the feature/remove-pretty-output branch from ca35fe3 to 238b401 Compare March 11, 2020 12:27
@webpack-bot
Copy link

Thank you for your pull request! The most important CI builds succeeded, we’ll review the pull request soon.

Copy link
Member

@rishabh3112 rishabh3112 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

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

Successfully merging this pull request may close these issues.

8 participants