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

git-modules

v0.1.20

Published

git-modules is a multi scoped npm-repository based on a single git repository.

Downloads

3

Readme

#git-modules git-modules is a multi scoped npm-repository based on a single git repository.

Setup

  • create a workspace (any directory will work)
  • create an empty "git-modules.json" inside your workspace (empty means "{}")
  • "git init" your workspace
  • create a package directory within workspace
  • create a scope inside the package directory (a directory starting with an "@" char)
  • create a node package inside a scope

If you did everything correctly, you should have a directory structure like this:

  • workspace/packages/@scope/mypackage/package.json
  • workspace/git-modules.json

HINT: You can change "@scope" to "@whateveryouwant"

Usage

Install git-modules

    npm install git-modules

Start repository server (cwd: workspace/node_modules/git-modules)

    node index.js

This will start a local bound npm server on port 9292 You can change the port by setting "port" in the "git-modles.json"

    {
        port:9393
    }

Publish your package (cwd: workspace/packages/@scope/mypackage)

   npm publish

Install the latest package

$ npm install @scope/mypackage

Install a specific version (use --save as usual if you want)

$ npm install @scope/[email protected]

Using npm to create a patch version (cwd: workspace/packages/@scope/mypackage)

   npm version patch

Republish your patched package (cwd: workspace/packages/@scope/mypackage)

   npm publish

Use your package

var mypackage = require('@scope/mypackage');

How it works

We create a http server to simulate a npm repository. Under the hood we start some shell git commands on every http request. "git archive" is used to create the tar package we send to the npm client. The publishing is based on git tags.

Problems ? Questions ? Answers ? Happy to hear.