You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to propose to update your @babel/code-frame to its newest version and at the same time move from chalk to picocolors.
As part of the ecosystem cleanup initiative (https://e18e.dev) we try to modernize and declutter the js ecosystem and also maybe reduce the size of your node_modules :D.
The newest version of code-frame dropped @babel/highlight as dependency and moved to picocolors as well. Therefore it would make sense to move to picocolors as well.
This would reduce the dependency count by a fair bit.
I would be happy to open a PR if you are up for this :)
The text was updated successfully, but these errors were encountered:
PR welcome, but this module hasn’t received an update in quite a while so should verify that it works with ESLint 9 before a release + needs to possibly set up release flow
I want to propose to update your
@babel/code-frame
to its newest version and at the same time move from chalk to picocolors.As part of the ecosystem cleanup initiative (https://e18e.dev) we try to modernize and declutter the js ecosystem and also maybe reduce the size of your node_modules :D.
The newest version of code-frame dropped @babel/highlight as dependency and moved to picocolors as well. Therefore it would make sense to move to picocolors as well.
This would reduce the dependency count by a fair bit.
I would be happy to open a PR if you are up for this :)
The text was updated successfully, but these errors were encountered: