Update chalk dependency

[guybedford]

💻

• Would you like to work on this feature?

What problem are you trying to solve?

I've just been running Babel core in Deno using JSPM import maps (https://generator.jspm.io/#W8nDwMDE7JSYlJqjkJ+n4JKal6/I4JAE4usn5xelOpjrGZrqGcCECopSi1NLdEsqC1KLk4syC0qg8gD3eyFFRwA) and there's an issue with Chalk 2.x because it mutates __proto__ which was banned by Deno in denoland/deno#4324.

Updating to Chalk 4 fixes the issue.

Describe the solution you'd like

Update to Chalk 4.

Describe alternatives you've considered

None

Documentation, Adoption, Migration Strategy

No response

[babel-bot]

Hey @guybedford! We really appreciate you taking the time to report an issue. The collaborators on this project attempt to help as many people as possible, but we're a limited number of volunteers, so it's possible this won't be addressed swiftly.

If you need any help, or just have general Babel or JavaScript questions, we have a vibrant Slack community that typically always has someone willing to help. You can sign-up here for an invite."

[hzoo]

Sounds good, can at least make a similar change to js-tokens for babel-highlight

babel/packages/babel-highlight/package.json

Lines 19 to 20 in 5fcf876

	"chalk": "^2.0.0",
	"js-tokens": "condition:BABEL_8_BREAKING ? ^7.0.0 : ^4.0.0"

[JLHwung]

Yeah we can't bump because Babel 7 still supports Node.js 6. We can, however, fork chalk and then proxy Node.js 6 users to our chalk@2 fork like we did for chokidar: https://github.com/nicolo-ribaudo/chokidar-2

[liuxingbaoyu]

#15814 Fixed in Babel 8