Hey @insin! We really appreciate you taking the time to report an issue. The collaborators
on this project attempt to help as many people as possible, but we're a limited number of volunteers,
so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack
community that typically always has someone willing to help. You can sign-up here
for an invite.

It looks like --quiet was removed in #7439 but it probably just wasn't fully thought through, not sure. Having it seems reasonable alongside the separate --verbose option.

Hey @loganfsmyth, I'd like to work on this. This will be my first contrib. 😃

@Rohanhacker go for it!

Hi @loganfsmyth @insin so would the --quiet option basically serve to remove the currently insuppressible console.log?
Also, which one would take precedence if a user passes in both --quiet and --verbose options?

Am I missing an issue in instead basing the lone console.log output to be conditional on ! cliOptions.verbose and not be required to add --quiet back?

Yes, I'd say it should disable all logging. My preference would be for --verbose alongside --quiet being an error.

Am I missing an issue in instead basing the lone console.log output to be conditional on ! cliOptions.verbose and not be required to add --quiet back?

I honestly don't feel strongly about it, you're right that we could absolutely just change it so that --verbose is required for the "Successfully compiled" message.

@Rohanhacker Have you looked into this at all at this point?

I haven't thought about the case when --verbose alongside --quiet is used. I was caught up with something. I'll make a pr tomorrow. I think throwing an error make sense when both are used together.

@loganfsmyth I've added the quiet flag, Should I make a pr or change it so that --verbose is required for the "Successfully compiled" message ??

hey @Rohanhacker do you still working at this issue? i've been looking any pull request opened by you but i have not found it

@thallysrc I've added quiet flag but not sure if it is required or not

Hey @loganfsmyth and @Rohanhacker ! Has this issue been solved yet? If not may I take a look at it? Thanks

When I upgraded to Babel 7, it stopped console logging the files that were transpiled. How can I get that logging back again? Now it only says Successfully compiled X files with Babel.

Any update on this for adding the --quiet flag back?