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

@marvinc.silva/sat

v1.0.1

Published

use samples as templates

Downloads

2

Readme

Samples As Templates

In a node project is common to have a folder structure where files follow some naming convention, to avoid copying and pasting on the folder's name and files you could type sat to use samples as templates

$ yarn global add @marvinc.silva/sat

Test it by checking the version

$ sat --version

You can also install it on the current project, for developers only.

$ yarn add @marvinc.silva/sat --dev

In this case you'll need to refer to the bin folder

$ node_modules/.bin/sat --version

WIP

This project is a work in progess, therefore, it only worries about happy scenarios, so there aren't any exception handling and somethings will change for sure.

We welcome suggestions as issues on github.

How to start using it

On your project's package.json file create an object sat, its keys will be considered as 'the name of your samples', and the value the sample itself.

  "sat": {
    "sampleA": "path\to\file.js",
    "sampleB": path\to\directory
  }

Commands

To duplicate a sample use:

sat use [sample] [name]

You can list all commands from the command line with:

sat list

Planned

sat create [sample]
sat delete [sample]