Comments (5)
Actually, looking into this a little more the package behaves differently depending on NODE_ENV which I think is unexpected for a sub module.
For example, when I ran into this error I tried to write a failing test, and I couldn't get it to throw an error because my tests are run with NODE_ENV="test", so in my case it's pretty much not possible to write a failing test without reconfiguring my test suite just for this one minor issue.
If you feel this behaviour is appropriate, you should definitely include it in the readme.
I think the best way to avoid unexpected behaviour is to avoid changing behaviour based on NODE_ENV.
from async-pool.
The assertions are meant to help during development (development only) by throwing exceptions on maluse instead of doing best effort to make it work. On the other environments, it should make best effort to make it work.
That being said, I don't recall why there's this check Parameter
array must have at least one item
. I agree it makes sense to support empty array. Can you submit a PR with a fix? Thank you
from async-pool.
Is the assertion during development thing a common convention ? I'm an amateur, but I've never encountered this before. I guess I'm just wondering whether you think it's worth a mention in the readme.
from async-pool.
No. We see that in some libraries (e.g., react.js), but I'd say the common convention is typed JS solutions like TypeScript or Flow.
from async-pool.
Now that this has been merged, can an updated package be published?
from async-pool.
Related Issues (20)
- how to kill this XD HOT 3
- Readability issue HOT 2
- Deno support HOT 1
- Typescript bindings HOT 4
- Chrome fails (Uncaught (in promise) TypeError: Failed to fetch) HOT 1
- another args to function HOT 1
- Failed to process the request HOT 3
- why using "array" as an input for iteratorFn() HOT 4
- Promise.allSettled() instead of Promise.all() option HOT 9
- question) How can i execute function with multiple arguments? HOT 1
- Benchmarks, overhead information HOT 1
- Unhandled rejections in some corner case HOT 2
- your code amazing!
- Allow for 1.x style await, without having to use for await HOT 9
- Feature: guarantee order of results HOT 3
- Does not "yield" reliably
- README.md usage issue HOT 2
- Allow iterable to be an async-iterable / async-generator HOT 2
- Add documentation about ordering no longer being preserved HOT 2
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 async-pool.