1c1a4de0e2
Part of #31506, this PR removes `loadEnvConfig` and `chalk` from the base server while keeping the same behavior for the node server. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have helpful link attached, see `contributing.md` ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have helpful link attached, see `contributing.md` ## Documentation / Examples - [ ] Make sure the linting passes by running `yarn lint`
19 lines
530 B
TypeScript
19 lines
530 B
TypeScript
// In the web runtime, we create an alternative object that just outputs the
|
|
// message to the console without any styling. The same APIs are supported
|
|
// for compatibility:
|
|
// - chalk.red('error')
|
|
// - chalk.bold.cyan('message')
|
|
// - chalk.hex('#fff').underline('hello')
|
|
const log = console.log
|
|
const chalk: any = new Proxy(log, {
|
|
get(_, prop: string) {
|
|
if (
|
|
['hex', 'rgb', 'ansi256', 'bgHex', 'bgRgb', 'bgAnsi256'].includes(prop)
|
|
) {
|
|
return () => chalk
|
|
}
|
|
return chalk
|
|
},
|
|
})
|
|
|
|
export default chalk
|