[NPMCLI-94] Use consistent logging style Created: 01/Feb/17  Updated: 03/Feb/17  Resolved: 03/Feb/17

Status: Closed
Project: Magnolia CLI
Component/s: None
Affects Version/s: None
Fix Version/s: 2.0

Type: Improvement Priority: Major
Reporter: Federico Grilli Assignee: Federico Grilli
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Sprint: Basel 81
Story Points: 3

 Description   

At the moment we're using several ways to display and colorize messages to users.

  • plain console.log(...)
  • helper. printError() | printSuccess() | printImportant() | printInfo() using the chalk library to colorize messages
  • npmlog package, the one used by npm itself.

We should decide for one approach and stick to it, so that CLI output looks consistent. I'd favour using npmlog for all of our messaging needs.


Generated at Mon Feb 12 04:46:28 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.