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 🙏

© 2026 – Pkg Stats / Ryan Hefner

cypress-should-really

v1.6.3

Published

Functional helpers for constructing Cypress should callbacks

Readme

cypress-should-really ci cypress version renovate-app badge

Read the blog posts Functional Helpers For Cypress Tests and Check Items For Duplicates

Example

Grab text from each list item, convert the strings into Dates, convert Dates into timestamps, then confirm they are sorted using chai-sorted assertion.

import { innerText, toDate, invoke } from 'cypress-should-really'
cy.get('.dates')
  .then(map('innerText'))
  .then(map(toDate))
  .then(invoke('getDate'))
  .should('be.sorted')

The above separates each operation using cy.then commands, which are not retried. Luckily, we can easily combine the individual steps into a single data transformation function using the pipe command.

import { innerText, toDate, invoke, pipe } from 'cypress-should-really'
const transform = pipe(map('innerText'), map(toDate), invoke('getDate'))
cy.get('.dates').then(transform).should('be.sorted')

The above commands are still NOT retrying the first cy.get command, thus if the page changes, the assertion still fails since it never "sees" the changed elements. We need to remove the .then(transform) step and directly tie the cy.get command to the assertion. We can move the data transformation into the assertion callback that transforms the data AND runs the assertion using really function.

import { innerText, toDate, invoke, pipe, really } from 'cypress-should-really'
const transform = pipe(map('innerText'), map(toDate), invoke('getDate'))
cy.get('.dates').should(really(transform, 'be.sorted'))

Finally, we can skip using the pipe function, since it is built into the really automatically. All functions before the assertion are applied and then the assertion runs.

import { innerText, toDate, invoke, really } from 'cypress-should-really'
cy.get('.dates').should(
  really(map('innerText'), map(toDate), invoke('getDate'), 'be.sorted'),
)

Installation

$ npm i -D cypress-should-really
# or install using Yarn
$ yarn add -D cypress-should-really

API

  • map
  • invoke
  • constructor
  • toDate (deprecated) use constructor(Date) instead
  • its
  • greaterThan
  • flipTwoArguments
  • partial
  • pipe
  • tap
  • filter
  • isEqual
  • really

invoke

invoke(<method name>, ...arguments) returns a function that waits for an object or an array, then calls the method and returns the results

const calc = {
  add(a, b) {
    return a + b
  },
}
invoke('add', 1, 2)(calc)
// 3

See invoke-spec.js

constructor

Takes a constructor function, returns a function that waits for a single argument and calls with the new keyword.

import {constructor} from 'cypress-should-really'
// converts a string to Date object
.then(constructor(Date))

tap

Passes the argument into the given function, but returns the original argument. Useful for debugging pipes of functions - insert it in every place of the pipeline to see the values.

const o = {
  name: 'Joe',
}
cy.wrap(o).should(really(its('name'), tap(console.log), 'equal', 'Mary'))
// change the name to Mary after some time
setTimeout(() => {
  o.name = 'Mary'
}, 1000)

In the above example, the console.log the string "Joe" multiple times, before logging "Mary" once and passing the test.

See tap-spec.js

Videos

See also

Small print

Author: Gleb Bahmutov <[email protected]> © 2021

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) 2021 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.