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

ohp

v1.0.1

Published

Overly-simple Hypertext Preprocessing

Downloads

3

Readme

ohp

A web framework of sorts to get you up and running quickly with minimal amounts of dynamic content. Pronounced 'ope', like the midwestern greeting to inanimate objects.

Think of this kind of like PHP. It's slightly less icky, even, and gets you to similar places.

Why?

Every so often, I have an idea for a silly web-based project. The professional in me says that I should use whatever the current community favorite framework is. This almost always takes me to Node, which takes me to a 12-layer dip of convoluted frameworks and transpilers and polyshim endofunctors that, by the time I'm up to speed and gotten code working, I'm tired, I'm overcaffeinated, I'm frustrated, the day is ruined, and I never actually get back to my silly idea. The world needs more silly projects, so here's a silly project to make other silly projects easier.

What is it really?

It's a simple node-based web server that can automatically render EJS templates. It's not fast and it's not pretty, but it works. I don't recommend running it in production (or really outside of an isolated container).

Installation

You'll need npm.

npm install -g ohp

Running

ohp <path-to-file-root>

For example, to run the hello-world example from this root of this repo:

ohp examples/hello-world

For command-line options, run ohp --help.

Running examples

Follow installation above. Clone this repo, then, from the root:

ohp examples/hello-world

If you don't want to install ohp globally, you can use yarn instead:

yarn && yarn start examples/hello-world

Either way, navigate to http://localhost:8080/ to check it out.

Dynamic content

ohp bundles EJS - any file ending with .ejs will be rendered as an EJS template (other files are just piped on through). Directories use index.html.ejs, index.ejs, or index.html in that order. Files can be requested without the .ejs extension and ohp will find them - for example, a request for /example.html will check if /example.html.ejs exists, and use it if it does.

Logging

ohp logs to standard out. Pipe that somewhere else if you need it somewhere else.

License

MIT