Closed rr326 closed 3 months ago
I think you might've hit the same issue as #399.
- import { concurrently } from "concurrently"
+ import concurrently from "concurrently"
should fix it.
@gustavohenke Thank you! That makes sense.
@rr326, Just fyi, this is really confusing, esp. since VSCode / TypeScript likes to import the named version automatically by default.
I'm so glad I stumbled across this closed issue; otherwise I would've given up.
Is this really not something that could be fixed or at least clarified? Is there ever even a reason to import the named version / does any project actually rely on it?
@gustavohenke Is there a way to throw a warning (console.log) if it is imported and used improperly? Or even just if it is imported this way? That might strike the right balance between not breaking anything, and preventing people from making this very hard to spot mistake.
As someone who uses tons of open source projects of which I just skim the docs, I really value when they print a warning saying, "Hmmm... are you really intending to use this in this really dumb way?"
Hey folks, your concerns should be fixed on the main branch by #456, it's just that there are a few other major/breaking changes coming along too.
@gustavohenke That's awesome. Thank you Gustavo.
Using the
concurrently()
API, it is not printing to stdout, unlessraw:true
.test.js
node test.js
No output.Set
raw:true
==> expected output