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

sectionify

v0.1.2

Published

CLI for single-file code dependency management

Downloads

11

Readme

sectionify.js

A CLI for building API-specific versions of single-file JS libraries

Installation

npm install sectionify

Usage

sectionify [--header=msg] input_file [dependencies]

In your code, mark sections and dependencies with //SECTION comments:

E.g. In sample.js:

var a = 'leading code is always included';
//SECTION foo
function hello(msg) {console.log('hello ' + msg);}
//SECTION bar REQUIRE foo
hello('do bar things');
//SECTION baz REQUIRE foo
hello('do baz things');
//SECTION
var b = 'trailing code is always included';

Then build section-specific scripts with sectionify. Only the required sections are kept:

> sectionify sample.js foo

var a = 'leading code is always included';
function hello(msg) {console.log('hello ' + msg);}
var b = 'trailing code is always included';

REQUIREed sections get included for you:

> sectionify sample.js narf

var a = 'leading code is always included';
function hello(msg) {console.log('hello ' + msg);}
hello('do bar things');
hello('do baz things');
hello('do narf things');
var b = 'trailing code is always included';

Build with multiple sections:

> sectionify sample.js bar baz

var a = 'leading code is always included';
function hello(msg) {console.log('hello ' + msg);}
hello('do bar things');
hello('do baz things');
var b = 'trailing code is always included';

Prepend a header string to the output:

> sectionify --header='// AUTO-GENERATED - DO NOT EDIT\n' sample.js

// AUTO-GENERATED - DO NOT EDIT
var a = 'leading code is always included';
var b = 'trailing code is always included';