fix(cli): errors not showing when using --log-levels CLI option

[moimael]

Syncpack version

14.0.0-alpha.10

Operating system(s)

Linux

Steps to reproduce

yarn syncpack lint failing on CI is hard to diagnose.

The error is lost in the middle of a lot of information, and since we don't have terminal colors, it's hard to spot.

I tried playing with log levels (yarn syncpack:lint --log-levels warn or yarn syncpack:lint --log-levels error), but unless it's on info I don't have any output, even when there is an error.

Expected behavior

We can configure the CLI to output errors only on CI.

Actual behavior

The CLI outputs the full info logs on CI.

Code of Conduct

• I agree to follow the Code of Conduct

[JamieMason]

Hey @moimael, you might want to wait until it is stable but this is done in v14 alpha via the --log-levels option.

Taken from npx syncpack@alpha lint --help

      --log-levels <log-levels>
          Control how detailed the log output should be

          Examples:
          Turn off logging completely
          $ syncpack lint --log-levels off
          Only show verbose debugging logs
          $ syncpack lint --log-levels debug
          Show everything
          $ syncpack lint --log-levels error,warn,info,debug

          [default: error,warn,info]
          [possible values: off, error, warn, info, debug]

[moimael]

Hey @JamieMason ! We are already on 14-alpha10! The log-levels option returns nothing in warn or error mode, even when there are errors. I only get the full output when I'm using info

[JamieMason]

Sorry I totally didn't read your issue properly, I'll try to reproduce and fix next time I work on syncpack. Should be a small job.

[JamieMason]

Ok, I think I see what's happening. You're expecting the log levels to apply to eg. version mismatches right? At the moment though that's not how that works, the error channel for logs refers to exceptions, like this example:

npx syncpack@alpha lint --source 404/package.json --log-levels error
✗ Found 0 package.json files

But, I think your idea / mental model is a better one. It'll be a bit more work but I think it would be better if it worked that way – so version mismatches appear on the error channel.

This is pretty convenient actually as I needed some way of showing only errors, for things like bringing back the list-mismatches command.

[moimael]

Ok, I think I see what's happening. You're expecting the log levels to apply to eg. version mismatches right?

Yes exactly! But I can see my assumption was wrong.

But, I think your idea / mental model is a better one. It'll be a bit more work but I think it would be better if it worked that way – so version mismatches appear on the error channel.

Indeed, It does seem like an implementation detail and not something I should be aware of as a user, but I'll let you decide what's best!