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

file-snippets

v1.1.4

Published

vscode code snippets generator

Downloads

2

Readme

snippets

vscode code snippet generator

INSTALL

npm i file-snippets -g

USAGE

Usage: snipp [options]

Options:
  -V, --version        output the version number
  -i, --input <path>   config input path
  -o, --output <path>  config output path
  -p, --prefix <name>  config prefix words, default equal inputpath basename, valid only if inputpath is a file
  -t, --title <title>  config title, default equal prefix, valid only if inputpath is a file
  -d, --desc <desc>    config description, default equal title, valid only if inputpath is a file
  -C, --no-comb        don’t combi output, valid only if input is a dir
  -c, --config <path>  set config file path
  -m, --merge <name>   merge to a json file
  -h, --help           output usage information

EXAMPLE

# help
snipp -h
# single file
snipp -i ./codes/a.js -t 'a demo' -p a -d 'a descrition' -o ./snippets
# by a config file
snipp -c ./snipp-demo.config.js -o ./snippets
# by a dir
snipp -i ./codes -o ./snippets
# merge exists json file
snipp -i ./codes -m javascript -o ./snippets
snipp -i './code/a.json,./codes/b.json' -m javascript -o ./snippets

config file like this

module.exports = {
  // set title as key
  'a demo': {
    // set prefix
    prefix: 'ad',
    // set body path
    body: './codes/a.js',
    // set description
    description: 'a demo description',
    // set type, exp:output in javascript.json
    type: 'javascript'
  },
}