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

redux-file-sync

v0.1.1

Published

Sync your redux actions to an external file system.

Readme

redux file sync

Sync your redux actions to a cloud storage file system.

Read the full documentation: https://alexishevia.github.io/redux-file-sync/

Development Info

Getting Started

  • Install nodeJS (v10.15.0 preferred)
  • Run npm install to install all dependencies

Running Tests

# Run all tests
npm run test

# Run a single test
npm run test <filename or path>
eg:
  npm run test my-test

# Run test using a debugger
npm run test-debug <filename>
eg:
  npm run test-debug my-test

Linting / Formatting Code

This project is configured to run prettier when you do a git add (using husky and lint-staged), so you don't need to worry about formatting code.

However, we still use eslint to capture syntax errors. The .eslintrc.json file is set to extend eslint-config-prettier, so eslint will only report on syntax errors instead of enforcing formatting.

Note:
Some editors will fail to load eslint from a pacakage's subdirectory, and will default to the global eslint - which might not have all the plugins you need.

If that happens, you'll need to manually specify the path to the correct eslint.

In my case, I had to create a local .vimrc file with:

let g:syntastic_javascript_eslint_exec='/home/alexishevia/Projects/Personales/redux-file-sync/node_modules/.bin/eslint'

Publish to npm

Run the following to publish the package to npm:

npm run build && npm publish

Documentation

The home page for the project lives in: https://alexishevia.github.io/redux-file-sync

It is generated from this repo's docs directory using Docsify.

You can run Docsify locally with:

npm run docs

Note:
Any PR that changes the architecture should also include updates to the Docsify documentation (to avoid code and docs going out of sync).