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

pnp

v0.0.3

Published

A terrible idea, realized

Downloads

2,199

Readme

PNP: Personal Node Pages

Do you ever think "man, node.js is great, but I wish I could just throw up a simple website fast like I could in PHP?"

Well, screw you, I built this anyway! PNP serves a website that consists of nothing but EJS templates and static files, from any folder you choose.

Update: PNP is now in production!

Installation

PNP is best used as a global utility:

npm install pnp -g

Usage

Switch to the directory containing your templates, and just run:

pnp

You're done! Your site is now available at http://localhost:5000.

If you want to get fancy, you can specify the host (or IP) and port:

pnp -p 8080 -h 192.168.0.101

By default, PNP listens on all available IPs. This is convenient but insecure.

Making a site

To create a new page in your site, simply create a file ending in .ejs and put it in the directory where you are when you run PNP. You can create as many as you want, and it understands folders and sub-folders. Anything that doesn't end in .ejs (like CSS, or image files) gets served straight up without any modification.

Templates

PNP uses EJS to do all templating. EJS is basically JavaScript used the way PHP or ASP pages are: HTML, with code embedded in the HTML. Here's an example template:

<%
var fun = function() {
  return "woo"
}
%>
<% title = 'Hello!' %>
<% include templates/header %>

<h1>Welcome!</h1>

<p>This is the home page. Here's <a href="/foo">foo</a> and <a href="/foo/bar">bar</a></p>

<p>Also <a href="/baz">baz</a> and <a href="woo">woo</a>.</p>

<p>The time is <%= new Date() %>.</p>

<p>Is this <%= fun() %>?</p>

<% include templates/footer %>

You can define and use functions, include other templates, and run arbitrary JavaScript in the template. You can also make use of variables in query strings. These are made available in a variable called _GET (oh yeah, I'm bringing it back). So if your URL is http://localhost/foo?x=y and you have a file called "foo.ejs" in your site, you can put the following code in it:

<p>The value of x is <%= _GET.x %></p>

And the page will print "The value of x is y". I will get around to POST variables at some point I'm sure.