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

@tagmedev/tagme-models

v9.2.0

Published

Database models for all Tagme applications.

Readme

TagmeModels

This project centers the mongoose models used by Tagme Node.js projects and is a npm private package.

Usage

  1. Make sure the project has the tagmedev npm login token file .npmrc inside the project root folder (i.e. the package.json containing folder);
  2. Include and install the @tagmedev/tagme-models module as a project dependency (e.g. npm install @tagmedev/tagme-models --save);
  3. Require the package on the script files as require('@tagmedev/tagme-models').
  • E.g. var AppsModel = require('@tagmedev/tagme-models').Apps;

Updating

  1. Clone this GitHub repository;
  2. Update the code as needed and push all your modifications;
  3. When you're ready to publish the new version, run npm version <patch|minor|major> -m '<message>'
  • Use patch when you made backwards-compatible bug fixes;
  • Use minor when you added functionality in a backwards-compatible manner;
  • Use major when you make backwards-incompatible changes;
    • On a branch other than master, you may also use prepatch, preminor or premajor to test new features;
  • Write a summary message for this new version;
  • Depending on the update type, npm will increase one of the version parts inside package.json respecting major.minor.patch, create a new commit and also tag this release.
  1. Push everything, including the tags: git push origin <branch name> --tags;
  2. Run npm publish.

Creating a new package

  1. Create a new GitHub repository and clone it;
  2. Copy the npm login token file .npmrc to the project root folder;
  3. Run npm init and follow the steps;
  4. Code the project as needed:
  • Suggestion: use an index.js file to export all modules coded inside a lib folder.
  1. Commit and tag this release, e.g.:
  • git add -A
  • git commit -m 'Initial release';
  • git tag v0.0.1;
  • git push origin <branch name> --tags.
  1. Run npm publish.