Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Making concurrently a purely ESM package #482

Closed
aqeelat opened this issue May 28, 2024 · 2 comments
Closed

Making concurrently a purely ESM package #482

aqeelat opened this issue May 28, 2024 · 2 comments

Comments

@aqeelat
Copy link

aqeelat commented May 28, 2024

Since concurrently is mostly run via CLI, what is stopping it from being converted to ESM? Are there any implications that are slipping my mind?

I'm willing to try converting it if the change would be accepted.

@gustavohenke
Copy link
Member

gustavohenke commented Jun 22, 2024

Hey! Nothing really stopping it, it's just that I wouldn't like to exclude some CJS users of the API.
I don't think there's any benefit of doing this change either, other than using newer versions of e.g. chalk?

Also a fun read:
https://www.reddit.com/r/node/comments/14rg9ym/esm_not_gaining_traction_in_backend_node/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Seems like the numbers are a bit dated, but chalk ESM-only is still 10x less popular than its previous, CJS version. chalk versions on npm

@gustavohenke
Copy link
Member

I'm closing this issue for now, but happy to read what others think.

@gustavohenke gustavohenke closed this as not planned Won't fix, can't repro, duplicate, stale Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants