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 🙏

© 2025 – Pkg Stats / Ryan Hefner

nppack

v0.2.2

Published

no paste pack for static html development

Downloads

17

Readme

nppack

no-paste-pack

motivation

when we develop server rendering project, we could use Bootstrap, it needs to paste more and more template html, so the project is very hard to development.

nppack is a way to help your use Component to development(if you follow some rules), at last the dist html is like to paste more and more template html, of course it is a work for nppack

quick-start

install

yarn add nppack

project-dir

│  config.json
│
└─src
    ├─admin
    │  ├─department
    │  │      Content.html
    │  │      Footer.html
    │  │      Header.html
    │  │      index.css
    │  │      index.html
    │  │
    │  └─user
    ├─css
    │      bootstrap.min.css
    │
    ├─image
    └─js
            bootstrap.min.js
            jquery.min.js

Config.json

{
  "src": "./src",
  "srcPublicJs": "./src/js",
  "srcPublicCss": "./src/css",
  "srcPublicImage": "./src/image",
  "srcPublicFonts": "./src/fonts",
  "srcPublicMedia": "./src/media",

  "dist": "./public",
  "distPublicJs": "./public/js",
  "distPublicCss": "./public/css",
  "distPublicImage": "./public/image",
  "distPublicFonts": "./dist/fonts",
  "distPublicMedia": "./dist/media",

  "port": 5500,
  "host": "0.0.0.0"
}

how to use

...
<div>
  <Header />
  <h1>nppack</h1>
</div>
...

index.html

...
<div>
  <h1>Header</h1>
</div>
...

Header.html

build

in the project root

# it will build
nppack build

# it will watch file and start devServer
nppack dev

in your config.json - dist: 'xxx' your xxx folder is result html

Rules

  1. in src folder the xxx/xxx/index.html will be used as a template

  2. in index.html, your component name must start with uppercase and in same path your Component.html's file name is same as Component name

<div>
  <Header>
  <h1>foo</h1>
</div>
|-- index.html
|-- Header.html
  1. public js, css, image's path is setting in config.json

  2. you could use js, css... they could copy to dist folder

|-- index.html
|-- Header.html
|-- index.css
|-- index.js
<link href="./index.css" rel="stylesheet">
...
<div>
  <Header>
  <h1>foo</h1>
</div>
...
<script src="./index.js"></script>