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

@iteam/create-templates

v1.6.1

Published

Iteam project templates with our preferred defaults and configurations

Downloads

2

Readme

👷‍♀️ templates 👷

This repository contains Iteam project templates to scaffold new projects and a small CLI to initialize them.

How to use

  1. In your terminal, run:
npm init @iteam/templates@latest
  1. You will be presented with the templates available (currently koa-typescript, react-typescript, react and vite)
  2. When you choose a template, a sub-directory with a new project will be created.

How to contribute

The CLI part of this project is responsible for "end user usage", as in when you use the CLI to install a new template. All the source code for the CLI is in the src directory.

When you run npm run build from the root, we bundle the source files into ./index.js. Later, when this CLI is used, said ./index.js is executed, effectively running the CLI script in the terminal of the consumer.

You can test the script locally by running:

npm run build
node index.js

This project is set up with semantic-release. Every push to the main branch will trigger a Github Actions workflow (./.github/workflows/release).

This workflow will do the following:

  • Run tests

  • Run npx semantic-relase, which will in turn:

    • Analyze the commits since the last release, using the commit names based on conventional-commits

    • If eligible*, create a new SemVer version tag based on the commit names

    • If eligible*, publish a new version of this library to NPM at @iteam/create-templates

    • If eligible*, append the new version to the changelog

      * Eligible means if the commits since the last release motivates a new release, where commit name fix: motivates a patch version, feat: motivates a minor version, and BREAKING CHANGE(footer) motivates a major version. Read more at conventional-commits