You went way out of your way to look like you invented nanocolors, when it's actually someone else's work whose background you intentionally hid

You should destroy this repository and apologize. All those users and that money belong to him, and you know it.

All of your work is now suspect.

I have removed your work from every repo I have control over, and I am encouraging everyone I know to do the same.

You are an unrepentant plagiarist demanding recognition from your victim.

Hey, I'm trying to use yours truly, nanocolors instead of chalk in a simple JS program and I keep getting this error when running npm test on the test.js file

App works perfectly fine when run, ( has import { red, blue } from 'nanocolors'; @ the top ) and the class tested is being exported.

Any ideas? Just substituting nanocolors imports and syntax to chalkmakes Jest run the test fine.🙆‍♂️

1. In the author section of "LICENSE" file, only copyright holders should be listed. It is true that Bucaran is the author of the colorette repo, but it doesn't mean that Bucaran automatically become a copyright holder of all derived works.

2. Since nanocolors is derived work of colorette which is licensed under MIT license, the colorette's LICENSE term should be included in nanocolors' source code. I know it's lengthy but this is the proper way to use MIT licensed source code. Look at this term:

   The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

By the way I'm grateful to see that Bucaran didn't DMCA takedown your repo this time.

node .\complex-benchmark.js
chalk          1,201,276 ops/sec
cli-color        135,233 ops/sec
ansi-colors      719,065 ops/sec
kleur          1,404,775 ops/sec
kleur/colors   1,471,413 ops/sec
colorette      1,603,018 ops/sec
felt-pen       1,489,272 ops/sec
nanocolors     1,674,054 ops/sec

chalk         101 kB
cli-color    1249 kB
ansi-colors    25 kB
kleur          21 kB
colorette      16 kB
felt-pen        6 kB
nanocolors     16 kB

Hey, welcome to the color space lol

You should be benching against kleur/colors module since that's the direct comparison to yours and colorette. The root kleur module is the chalk API which is slower, slower to load, and not tree shakable by design.

Thanks :)

People like chalk’s template API a lot. We need to find a way to copy it in a form:

import { colorize } from 'nanocolors'

colorize`CPU: {red ${cpu.totalPercent}%}`

I like to do this in my test

import chai from 'chai';
import { isColorSupported  } from 'nanocolors';
import { executeCli } from './test-helpers.js';

const { expect } = chai;

describe('cli', () => {
  before(() => {
    // ignore colors in tests as most CIs won't support it
    isColorSupported = false;
  });

which fails as you can't change variables you import?

maybe isColorSupported should be an object?

or is there another way to disable it while running the test locally that does not require a cli flag?

index.browser.js wouldn't actually work in a browser since its a commonjs module.

what'd be really nice is to replace this with an ES module ("module": "ES2020" for example when running tsc).

then we would be able to load the module directly in browsers, deno, node ESM, etc.

though you may need to add an exports field in your package.json to make node detect it properly:

  "exports": {
    "import": "./index.browser.js",
    "require": "./index.js"
  },

node .\loading.cjs
chalk         13.964 ms
cli-color     98.851 ms
ansi-colors    3.832 ms
kleur          7.182 ms
kleur/colors   1.469 ms
colorette      2.221 ms
felt-pen       1.424 ms
nanocolors     2.494 ms

It seems migration from chalk to nanocolors can be easily automated using jscodeshift. I made the simple transformer (I put in a gist here and added instructions of how apply it in the README

Just released Colorette 2.0.11 with further perf improvements. This is what I'm seeing in the CI.

• https://github.com/jorgebucaran/color-bench-test/runs/3710045880?check_suite_focus=true

If you run your benchmarks in the CI you'd avoid copy & pasting from your terminal all the time.

Would be nice if you could update your README with these results (or remove outdated results).