The world is not ready for esm yet

[alexeyraspopov]

Rationale

With this PR we break any possible compatibility with nanocolors and colorette for the sake of larger ecosystem support, smaller package size, and the ability to enforce color (via custom API).

• Supporting ESM-first is just too much pain (Fix React Native support #25, Add CJS version #2). Maybe the story will change in a year or two
• Tree-shaking is not beneficial for a library which primary use is Node.js CLI tooling
• Import of an API object is more flexible than adding every single formatting function to the import

Additionaly, I decided to make another change here, while I'm at it: using tabs instead of spaces. Because I like tabs with size 2 and it also reduces package size. The PR includes .editorconfig so everyone who's using the plugin should be fine. Also, GitHub properly supports it on the website.

Preliminary checking the package size (via clean-publish and npm publish --dry-run) shows following stats:

package size:  2.4 kB
unpacked size: 5.6 kB

That's a win-win

Closes #4
Closes #13
Closes #22
Closes #25

[ai]

Need createColors type too.

[alexeyraspopov]

@ai, I made another attempt to do .d.ts but I need someone to verify it since I'm not quite good at it

[ai]

@alexeyraspopov .d.ts looks good, but createColors’s result doesn’t have createColors. It is better to use:

export type Formatter = (input: string | number | null | undefined) => string;

export interface Colors {
	isColorSupported: boolean;
	reset: Formatter;
	bold: Formatter;
	dim: Formatter;
	italic: Formatter;
	underline: Formatter;
	inverse: Formatter;
	hidden: Formatter;
	strikethrough: Formatter;
	black: Formatter;
	red: Formatter;
	green: Formatter;
	yellow: Formatter;
	blue: Formatter;
	magenta: Formatter;
	cyan: Formatter;
	white: Formatter;
	gray: Formatter;
	bgBlack: Formatter;
	bgRed: Formatter;
	bgGreen: Formatter;
	bgYellow: Formatter;
	bgBlue: Formatter;
	bgMagenta: Formatter;
	bgCyan: Formatter;
	bgWhite: Formatter;
}

export = Colors & { createColors: (enabled: boolean) => Colors };

Also, it is useful for some TS projects to be able to re--use Formatter and Colors types.

[TrySound]

Explicit commonjs exports allows to use named imports in node

exports.red = red;
// usage
import { red } from 'picocolors';