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

@spbarker/vision

v2.1.0

Published

Pomodoro timer with electron and react

Downloads

3

Readme

CircleCI JavaScript Style Guide Coverage Status Commitizen friendly semantic-release

Vision

Pomodoro style timer for Mac OS written using Electron & React!

Getting Started

  • yarn start will compile all of the necessary JS and run the electron application.
  • yarn js:lint will lint the application.
  • yarn test:coverage will run the unit tests.

Linting

Linter of choice is StandardJS.

Installing the application locally

To build the app itself and install it to your applications run yarn dist and then open the dmg present in dist/.

Contributing

Commiting

All commit messages should be done through Commitizen, which is configured to use the @metahub/cz-conventional-commit adapter. These are installed locally through dev dependencies.

To commit through Commitizen, just run yarn cm, and follow the interactive prompt. This enforces proper semantic versioning and releasing with CI.

Reviewing

master branch is protected and required two reviews to be merged.

Testing

pre-commit and pre-push hooks have been set up using husky to enforce that unit tests and linting are both run at these points.

The test coverage is enforced at 100% across the board - no exceptions. All of the tests should pass with 100% coverage for a PR to even be considered for review.

CI

The CI tool of choice is CircleCI and runs on every pull request, not every commit however. The CI will run yarn install, linting, unit tests, and then finally a JS build to ensure that everything is in working order.

Releasing

Releasing is handled automatically by CI. The versioning is handled itself by a tool called semantic-release.

Once this has completed a new git tag will be created. However the version in package.json will not have been updated. This job will need to be done separately.