Skip to content

[BAE-219] Change out Chalk to styleText from Node#243

Open
dmiller113 wants to merge 3 commits intomainfrom
dmiller113/BAE-219-remove-chalk
Open

[BAE-219] Change out Chalk to styleText from Node#243
dmiller113 wants to merge 3 commits intomainfrom
dmiller113/BAE-219-remove-chalk

Conversation

@dmiller113
Copy link
Copy Markdown

@dmiller113 dmiller113 commented Mar 20, 2026

Addresses
Issue #219

Changes

  • Changes out calls to the chalk library, to use node's styleText out of the util library.
  • Bumps up the engine inside package.json to 20.12.0

Rovo Dev code review: Rovo Dev couldn't review this pull request
Upgrade to Rovo Dev Standard to continue using code review.

@changeset-bot
Copy link
Copy Markdown

changeset-bot Bot commented Mar 20, 2026

🦋 Changeset detected

Latest commit: 46e4fa8

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

@dmiller113
Copy link
Copy Markdown
Author

I am not exactly sure that bumping the engine up to node 20 is a patch upgrade in semver; any feedback on that choice is appreciated.

Comment thread package.json
"module": "./lib/esm/index.mjs",
"engines": {
"node": ">= 18.20.6"
"node": ">= 20.12.0"
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

This needs to be a major bump.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

Will do.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

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

What else, if anything, should be added to help the pipeline test suite to understand the shift to node 20.12.0? There's several automated comments around styleText not existing, and I imagine it's flagging the changes as unmergable.

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.

2 participants