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

@moritzboeckelmann/snippets

v1.0.1

Published

This packages provides functions to use snippets in any javascript or typescript easily

Downloads

5

Readme

Snippets

Introduction

Key Facts

Getting Started

Configuration

To configure the snippet package, a JSON File is needed. The default path to your config file ongoing from your project root folder is ./snippet/config.json.

If you want to use another location or an error occurs you can specify a path (absolute) in your .env by adding the variable SNIPPET_CONFIG_PATH. As of now those config files contain the default config for your snippet service.

In case you want to use a separate instance with different configurations to your default, you can parse an object in, which contains all the configurations you want to override.

If you provide no configuration at all the package will fall back on the standard configuration. Below you will find an explanation and the possible values likewise the fall back value of every available configuration.