npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, πŸ‘‹, I’m Ryan HefnerΒ  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you πŸ™

Β© 2024 – Pkg Stats / Ryan Hefner

cypress-await

v1.6.12

Published

Cypress async await magic πŸͺ„

Downloads

8,185

Readme

cypress-await cypress version

Cypress spec preprocessor that adds the "async / await" syntax

Examples

πŸŽ“ Covered in my Cypress Plugins course

Todos

  • switch from @cypress/browserify-preprocessor to @cypress/webpack-batteries-included-preprocessor for bundling transpiled spec

Install

Add this package as a dev dependency

$ npm i -D cypress-await
# or using Yarn
$ yarn add -D cypress-await

Use as a preprocessor

Add the following to your cypress.config.js file:

// cypress.config.js
const { defineConfig } = require('cypress')
// https://github.com/bahmutov/cypress-await
const cyAwaitPreprocessor = require('cypress-await/src/preprocessor')

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      on('file:preprocessor', cyAwaitPreprocessor())
    },
  },
})

In your spec files you can use value = await cy... instead of cy....then(value => )

it('shows the number of projects', async () => {
  await cy.visit('/')
  const n = await cy.get('#projects-count').invoke('text').then(parseInt)
  cy.log(n)
  expect(n, 'number of projects').to.be.within(350, 400)
})

The above code is equivalent to the "plain" Cypress test

it('shows the number of projects', () => {
  cy.visit('/')
  cy.get('#projects-count')
    .invoke('text')
    .then(parseInt)
    .then((n) => {
      cy.log(n)
      expect(n, 'number of projects').to.be.within(350, 400)
    })
})

Preprocessor sync mode

It might seem redundant to always write n = await cy..., thus there is a "sync" mode preprocessor where you can write the spec code without using await before each Cypress chain.

// cypress.config.js
const { defineConfig } = require('cypress')
// https://github.com/bahmutov/cypress-await
const cyAwaitPreprocessor = require('cypress-await/src/preprocessor-sync-mode')

module.exports = defineConfig({
  e2e: {
    setupNodeEvents(on, config) {
      on('file:preprocessor', cyAwaitPreprocessor())
    },
  },
})

We can get the parsed number of projects from the page

it('shows the number of projects', () => {
  cy.visit('/')
  const n = cy.get('#projects-count').invoke('text').then(parseInt)
  cy.log(n)
  expect(n, 'number of projects').to.be.within(350, 400)
})

Transform some spec files

You can apply this preprocessor only to some specs using minimatch over the full spec source filepath

setupNodeEvents(on, config) {
  on('file:preprocessor', cyAwaitPreprocessor({
    specPattern: '**/*.sync.cy.js'
  }))
}

For simplicity, you can also use the end of the files that need to be transpiled. For example, to transpile all files that end with .sync.cy.js, you can use specPattern: '.sync.cy.js'

Show transpiled output

Set the preprocessor with the debugOutput: true option

setupNodeEvents(on, config) {
  on('file:preprocessor', cyAwaitPreprocessor({
    debugOutput: true
  }))
}

The transpiled output will appear in the terminal.

Debugging

Start Cypress with OS environment variable DEBUG=cypress-await

# on Mac or Linux
$ DEBUG=cypress-await npx cypress open

To see even more output enable the verbose debug logs with DEBUG=cypress-await:verbose

# on Mac or Linux
$ DEBUG=cypress-await:verbose npx cypress open

Small print

Author: Gleb Bahmutov <[email protected]> Β© 2023

License: MIT - do anything with the code, but don't blame me if it does not work.

Support: if you find any problems with this module, email / tweet / open issue on Github

MIT License

Copyright (c) 2023 Gleb Bahmutov <[email protected]>

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.