Bluebird VS browserify

It might, if the code can be optimized. There are all sorts of reasons why it might not. For example, at one point in time, a switch statement with more than 128 cases could not be optimized.

https://github.com/petkaantonov/bluebird/wiki/Optimization-k...

Prior to ES6, we used bluebird or Q. Now we have Promises natively:

For example: https://github.com/petkaantonov/bluebird/wiki/Optimization-killers

The standard library is quite barebones so you’ll need to import something else (Think bluebird for JS). You need an executor to run a future. I recommend using https://github.com/tokio-rs/tokio and reading their documentation.

I had a look at the bluebird promise FAQ, in which it mentions that .then(success, fail) is an antipattern. I don't quite understand its explanation as for the try and catch.What's wrong with the following?

I have not looked into how packages like bluebird does this, but I expect it is similar to the above items I expressed

You can look at the implementation of Bluebird an implementation of Promises that preceded them being available in JS itself.

Browserify to use node packages in the browser.

Browserify is a widely used JavaScript bundler with over 2 million NPM weekly downloads. In addition to Node.js support, allowing developers to use require() statements in the browser is one of its highlighted features.

This began to change when NPM came in and running npm install became a quick and easy way to install dependencies. Browserify became the first JavaScript bundler. As its documentation says -

Using Npm Module with Browserify

https://www.npmjs.com/package/browserify probably a little old school, but browserify is probably good enough.

One problem was to run jsDOM as UMD module. But luckly I was able to use browserify to compile jsDOM into UMD.

Browserify

https://browserify.org/ is an easy one to get started with.