Move to class-based construction

@sindresorhus right now, we use a traditional function/prototype build up of the Chalk class.

This has the negative side effect that in order to enable templating on custom contexts, you have to omit new - which is counterintuitive.

const ctx1 = chalk.constructor();
const ctx2 = new chalk.constructor();

const str1 = ctx1`hello`; // OK
const str2 = ctx2`hello`; // Error

Unless I’m mistaken, we can leverage constructor()'s ability to return a completely different object (even with new) to allow templates on all new chalk functions.

class Chalk {
    constructor(...) {
        // ... build up chalk template function ...
        return chalkTemplate;
    }

    // ...
}

const ctx = new Chalk();

const str = ctx`hello!`; // OK

Is this something we should do?

// cc @sindresorhus

tom-sherman earned $60.00 by resolving this issue!

• Checkout the Issuehunt explorer to discover more funded issues.
• Need some help from other developers? Add your repositories on Issuehunt to raise funds.

[Qix-]

@issuehuntbot don’t care about seeing funding status - that’s cool and all - but we can already see when people submit PRs. Don’t need you to mirror that data, it just causes noise.

cc @Rokt33r

[IssueHuntBot]

@tom-sherman has submitted a pull request. See it on IssueHunt