I'm not at a machine right now that I can test this; does this apply to e.g. chalk.red or only the root chalk object?

A better option might be to do:

Object.setPrototypeOf(Chalk.prototype, Function.prototype);

@ExE-Boss Hmm, actually, Chalk is already a function, so it should already have the function prototype, but then why isn't it working as it is? 🤔

function Chalk () { ... }

const chalk = {}
chalk.template = (...arguments_) => chalkTag(chalk.template, ...arguments_)

Object.setPrototypeOf(chalk, Chalk.prototype)
Object.setPrototypeOf(chalk.template, chalk)

Shouldn't the prototype chain here be chalk.template -> chalk -> Chalk.prototype -> Function.prototype? Or am I missing something? 🤔

The prototype chain is: chalk.template → chalk → Chalk.prototype → Object.prototype → null.

Hmm, I just don't understand why Chalk.prototype is pointing to Object.prototype when it's just defined as a function in the code. I mean obviously I'm missing something 😁

That’s standard ECMAScript behaviour: https://tc39.es/ecma262/#sec-makeconstructor.

The prototype property of constructable functions is initialised to a plain object with its prototype set to Object.prototype.

This object is used to create new instances by the new operator and to check for inheritance by the instanceof operator.

Ahh, of course 🤦‍♂

Thanks for pointing me in the right direction!

Yeah, doing Object.setPrototypeOf(Chalk.prototype, Function.prototype) is probably a better option, will update the PR 👍

Ping @LinusU

Closing for lack of response.

Sorry for the lack of response. I don't personally need this anymore since I don't use apply now that ... is natively supported.