Comments (7)
I think you might've hit the same issue as #399.
- import { concurrently } from "concurrently"
+ import concurrently from "concurrently"
should fix it.
from concurrently.
@gustavohenke Thank you! That makes sense.
from concurrently.
@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?
from concurrently.
@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?"
from concurrently.
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.
from concurrently.
@gustavohenke That's awesome. Thank you Gustavo.
from concurrently.
Related Issues (20)
- Please change the name of the project HOT 1
- Teardown command? HOT 3
- ERR_UNHANDLED_REJECTION with `killOthers` HOT 2
- Shortcut for `node --run <script name>` HOT 1
- Parallel-serial-parallel flow orchestration? HOT 1
- Deprecation warning with Node 22 HOT 8
- on sending --kill-others process ng serve close with exit code 1 - Still a problem HOT 2
- Making concurrently a purely ESM package HOT 1
- Does concurrently work with yarn2, yarn3, yarn4? HOT 1
- on sending --kill-others process ng serve close with exit code 1 - STILL HAVE A ISSUE =) HOT 3
- Try setting the `--success` flag, it allows you to set which process(es) you want to infer the exit code 0 from. HOT 1
- escaping pass-through arguments is too eager HOT 4
- ERR_REQUIRE_ESM HOT 2
- Exiting with code 1 on Linux HOT 7
- DeprecationWarning: The `util._extend` API is deprecated HOT 6
- TypeScript types are wrong when `module` is `node16` HOT 3
- `killOthers` won't fully terminate others if also `restartTries >= 1` HOT 2
- Make command more readable HOT 1
- Always exits 0 in monorepo HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from concurrently.