Bluebird VS step

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.

import { When, Then, Given } from '@badeball/cypress-cucumber-preprocessor'; Given(`I've opened the npm.com`, () => { cy.visit('https://www.npmjs.com/'); cy.intercept('GET', 'https://www.npmjs.com/search/suggestions?q=step', [ { name: 'step', scope: 'unscoped', version: '1.0.0', description: 'Test', date: '2017-01-06T21:16:57.341Z', links: { npm: 'https://www.npmjs.com/package/step' }, author: { name: 'John Smith', email: '[email protected]', username: 'test' }, publisher: { username: 'test', email: '[email protected]' }, maintainers: [{ username: '[email protected]', email: '[email protected]' }], }, ]).as('getResults'); }); When('I typed a phrase in the search field', () => { cy.get('input[name="q"]').type('step'); }); Then('I should see the results in the dropdown menu', () => { cy.wait('@getResults'); cy.get('ul[role="listbox"] li').should('have.length', 1).should('have.text', 'stepTest1.0.0'); });