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

@researchgate/node-package-blueprint

v0.3.1

Published

Blueprint for scaffolding new node packages

Downloads

25

Readme

Simplify the creation and open sourcing of front-end projects:

  • 👩‍💻  Start From CLI: generate the perfect starting blueprint for your new project
  • 📐  Project Layout: follow a clear and pre-defined project structure to ease the way to open sourcing
  • 🔧  Integrated Tooling: conciously chosen set of tools, configured and accessible via npm/yarn scripts
  • 🎡  Automated tasks: from commit message checking to changelog generation for releases

We want to make the process of open source projects at ResearchGate simple, and conventional.

When we create a new project, there are a lot of open questions around on how to best structure, document, and which tools to use.

This project provides the guidelines that clarify and facilitate this process.

Getting started

Install Node Package Blueprint as a global npm package:

npm install -g @researchgate/node-package-blueprint

Now create a new project with the CLI tool:

node-package-blueprint my-project
cd my-project/

🏁  Your project is ready! Take a look at the folder contents and when ready, install the dependencies:

yarn install

Once you're ready to release a new version use:

yarn release

This script will calculate the version number based on your commit history – make sure to follow the conventional commits guidelines. The CHANGELOG.md file is automatically updated with the relevant changes.

If it's your first release, you probably do not want to bump a new version into the history.

In such cases, use the --first-release flag:

yarn release -- --first-release

Documentation

Our documentation is structured in sections directly available under the docs folder:

Contributing

We'd love your help on creating Node Package Blueprint!

Before you do, please read our Code of Conduct so you know what we expect when you contribute to our projects.

Our Contributing Guide tells you about our development process and what we're looking for, gives you instructions on how to issue bugs and suggest features, and explains how you can build and test your changes.

Haven't contributed to an open source project before? No problem! Contributing Guide has you covered as well.