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

csnp

v1.4.1

Published

A cli-tool for generating VSCode code snippets.

Downloads

34

Readme

Install

pnpm i -g csnp # recommend

npm i -g csnp

yarn i -g csnp

bun i -g csnp

csnp

Using interactive prompts to generate .csnp files for managing vscode code snippets.

Rule csnp Path

The expected path for your snippets is:

.csnp/{SnippetType}/{SnippetName}.csnp

For example:

.csnp/js/log.csnp

SnippetType: js
SnippetName: log

Details

Open the file .csnp/js/log.csnp and edit the default code snippets as follows:

---
name: Log
prefix: '-log'
description: log something
---

code snippets
  • name: The name of the snippet.
  • prefix: The trigger text for the snippet in editor.
  • description: A brief description of what the snippet does.
  • code snippets: The actual code that will be inserted.

Just edit and replace the line code snippets of console.log.

---
name: Log
prefix: '-log'
description: log sth
---

console.log($1)

After editing, use the command:

csnp push

Then in editor you need to type the prefix -log and press Enter to generate the code.

Transforming Snippets

You can transform all .csnp files and store them locally or globally(in VSCode).

# local (default)
$ csnp push

# global (VSCode)
$ csnp push --global

Syncing Snippets

To sync all snippets from local or global(VSCode) and store them in .csnp directory.

# local (default)
$ csnp pull

# global (VSCode)
$ csnp pull --global

Usage Information

# csnp -h
csnp --help

Links

How to use Snippet in Visual Studio Code.

License

MIT @ Junxio.