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-redux-persist

v1.0.2

Published

This is just a bunch of hooks and Cypress commands that will assist you in dealing with the `redux-persist` package. It's not complete, and it works on a lot of assumptions about your setup.

Downloads

15

Readme

Cypress Redux Persist

This is just a bunch of hooks and Cypress commands that will assist you in dealing with the redux-persist package. It's not complete, and it works on a lot of assumptions about your setup.

Configuration

When testing, you will need to add the redux store into the window object so that Cypress is able to grab onto it. You can do this somewhere in your store initialization code. You will want to add:

if(window.Cypress) {
   window.store = store;
}

Where store is your redux store object.

Doing this allows Cypress to hook into the store object and invoke functions.

Pitfalls

The nature of redux-persist is that during it's hydration process, it will grab the localStorage key persist:root or whatever you've named your store and then inject it into the redux store at run time. This presents an issue with Cypress as the localStorage is cleared out any time a test finished or the page reloads.

For applications that rely on redux having persistant data, this obviously makes things impossible to test. This package attempts to solve that problem by using two functions - saveReduxStore and loadReduxStore.

Calling saveReduxStore will persist (inside Cypress) all the values currently in the redux store.

Calling loadReduxStore will retreive those values and using persist/HYDRATE will insert them into Redux.

Cypress is funny in that if you ever call cy.reload() it will blow the localStorage away, which isn't the expected behaviour in a live browser, but to recover your redux store, you can simply change cy.reload().loadReduxStore() and all data saved to this point will be re-injected into Redux.