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

versus-common

v1.3.2

Published

Common repo for business logic and redux for Vesus Client apps

Downloads

3

Readme

🔮 Versus [COMMON]

Useage

npm i --save versus-common

The package will expose 2 objects

  • actions
  • reducers

import {getAllTeams} from 'versus-common/actions'

Update: At this stage each client has to combine reducers and create the store itself. I will look at doing this on the common side. Then the client just needs to provide it to the root component.

Contribute

All code is done in the ./src in es6

Everything should be COVERED in tests. This project does not have a client whcih we can use to test - therefore everything must be done programmaticaly through tests.

Linting TBC

Build

Run npm run build to compile the src (es6) folder into ./build (es5)

Only the src/lib, src/classes and src/data are compiled into ./build. This is because the actions, middleware and reducers and straight imported in the client projects which will inturn compile the es6 with webpack. This may change depending on test... TBC

Test

Jest is the test runner and looks for the .test.js files in ./build

This means we can use es6 syntax like imports in our tests.

To test run npm run test or npm run test:watch when developing.

The build process will run before each test run ensuring the latest copy of the src is being tested.

Deploy

npm run deploy