Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@hyperupcall
Copy link
Contributor

@hyperupcall hyperupcall commented Dec 20, 2024

As mentioned in #639, the vendored supports-color only properly handles navigator being undefined since this commit, which was released in version v10.0.0.

This updates the vendored supports-color to v10.0.0 to fix that issue.

Initially, I copied the files over byte-for-byte and tried to fix errors with dependencies and CI. That was very silly, so I've simply applied the required changes from supports-color (in a different branch).

Closes #639

package.json Outdated
"sideEffects": false,
"engines": {
"node": "^12.17.0 || ^14.13 || >=16.0.0"
"node": ">=18"
Copy link
Member

Choose a reason for hiding this comment

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

We don't plan to do a major release for Node.js 18 support. It's not worth having to do a major release.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Oops, you're totally right! I have simplified my approach in #642, which supersedes this PR

@hyperupcall
Copy link
Contributor Author

This is superseded by #642

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.

Not handling navigator being undefined

2 participants