Is-promise Alternatives

Similar projects and alternatives to is-promise

guide

26 15,283 4.7 Makefile is-promise VS guide

The Uber Go Style Guide.
Developer-Style-Guides

11 3 10.0 is-promise VS Developer-Style-Guides

Style guides from Google, Facebook, Airbnb, Khan Academy and other tech organizations. Covers JavaScript, Swift, Java, Kotlin, and other popular languages. Made for developers by https://hotpot.ai.
SurveyJS

surveyjs.io featured

Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.

NOTE: The number of mentions on this list indicates mentions on common posts plus user suggested alternatives. Hence, a higher number means a better is-promise alternative or higher similarity.

Suggest an alternative to is-promise

is-promise reviews and mentions

Posts with mentions or reviews of is-promise. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2022-11-18.

Google’s Go Style Guide
3 projects | news.ycombinator.com | 18 Nov 2022

There's definitely a balance to strike.
On the one hand, you don't want to be constantly re-inventing the wheel. If someone has made a great package for doing a specific thing you need (printing data in tables, making ergonomic http requests that cover edge cases, reading an epub file, etc), then IMO you're better off using theirs. They care about it, they've tested it, and the implementation of it is one less thing you have to think about it. If you consider that every line of code that you write/maintain is a liability, then offloading that to others is very convenient.
On the other hand, external packages typically come without guarantees. Their owner/maintainer could lose interest, get hit by a bus, get hacked, anything. You're running their code in your projects and suddenly, all this uncontrolled code becomes the liability. You'd do best to do _everything_ in house in order to limit your external risk.
Ultimately, I think there's no single right answer here. Sure, you probably shouldn't add dependencies for things like "left-pad", but the line is a little blurrier for things like npm's "is-promise". It sounds simple enough (and the implementation [0] is only a 3-line function), but I'm unlikely to have written it correctly if I did it from scratch. Plus, it's tested! And lastly, I think your risk is lower the larger an external dependency is. Large projects, like React or Django, are much more upside than liability; it's everything in the medium range that you really need to consider.
[0]: https://github.com/then/is-promise/blob/ec9bd8a3f576324a1343...
logical and without ampersand and in JS
1 project | /r/programminghorror | 7 Oct 2021

oh, yea, i remembered the issue wrong. they used double bang to check if a value is truthy, not because single bang does not return a boolean.