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

sync-modules

v0.1.0

Published

automatically keep node_modules in sync with Git hooks

Downloads

7

Readme

sync-modules

js-standard-style

This package may be interesting to you if you're developing using Node.js and Git.

The Problem

At the beginning of your workday you git pull the latest changes from your coworkers and start working. After a while you notice that some of the tests aren't passing. You back out your changes and the tests still won't pass! How is this possible? You know you've configured GitHub to protect the master branch so it can't be changed without passing tests and this shouldn't happen.

The problem is that you haven't brewed your morning tea yet and you forgot to type npm install after git pull. Your package.json file and node_modules directory are out of sync. Oops!

The Solution

$ npm install --save-dev sync-modules

That's it; no configuration necessary. Installing the sync-modules package installs Git hooks to keep your node_modules directory in sync automatically with package.json when Git changes it.

It won't install if you already have a post-checkout or post-merge Git hook defined. I welcome a pull request if this case is important to you.

Credit

Thanks to David Walsh for the inspiration.

Copyright

Copyright 2016 David Braun

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/.