Fix export default for all colors

[rwu823]

Problems

For example if I do this, will get an error:

import c from 'colorette'

// types safe but get the error in runtime.
c.cyan('hello') // TypeError: Cannot read properties of undefined (reading 'cyan')

And then need to change to:

import * as c from 'colorette'

c.cyan('hello')

So I'm not sure if there was a special reason for this design? otherwise the general import usage case would be more reasonable and matched the type system.😅

[kibertoad]

Doesn't that break on systems that do not support ESM imports?

[rwu823]

@kibertoad not sure, still need to testing. But I think rollup will handle that?

[kibertoad]

Needs testing!

[kibertoad]

I remember default exports being a problem even with rollup, that was mentioned e. g. in Webpack project

[rwu823]

rollup will transform output to cjs version. So there should be no problem here is about "systems that do not support ESM imports"

And I tried that import or require from output file as es5/es6/ts they are all worked.

[jorgebucaran]

What you say about the types is true, but it was probably a mistake since I didn't intend to support default exports.

Named exports, default exports, or both? Which one is more idiomatic in Node? Should we even have a default export?

[rwu823]

@jorgebucaran Well, if you don't intend to support default exports, you should fix types avoid a mistake for users.

Also chalk did export default if this project expects as a alternative.

[jorgebucaran]

Of course. Can you show us how to fix them? As I said, this was likely a mistake, because I didn't intend to support default exports when I wrote the types.

Now, I'm open to discussing adding them in the future.