Skip to content

Conversation

@dreyfus92
Copy link
Contributor

closes: #119

@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 7, 2025

Open in StackBlitz

npm i https://pkg.pr.new/e18e/cli/@e18e/cli@122

commit: 3cd1dc8


let message = `${severityColor('[duplicate dependency]')} ${colors.bold(duplicate.name)} has ${duplicate.versions.length} installed versions:`;
// Disable colors completely when NO_COLOR is set (for consistent test snapshots)
const noColor = process.env.NO_COLOR === '1';
Copy link
Contributor

Choose a reason for hiding this comment

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

why?

this feels like a workaround rather than a necessity.

are you doing this because we didn't have any snapshots yet which use colours? we should just set FORCE_COLOR to 1 in the vitest config env (although vitest 4 might already do this)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

indeed it was a workaround cause i couldn't make the tests work properly even after updating the snapshots.

@43081j
Copy link
Contributor

43081j commented Nov 10, 2025

i think we need to hold off on this change until i finish aligning a bunch of the logic with the e18e github action

as it will change quite a lot of the inner workings

ill get back to it once i merge that stuff 👍

@dreyfus92
Copy link
Contributor Author

is there anything i can help you with?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

cli fails ugly when running in a non-package

2 participants