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

hyperloop-website

v0.0.1

Published

Hyperloop website V3

Readme

Hyperloop Website V3

## Work in progress!

The new website will:

  • be a 100% Hyperloop SPA (featuring Components, Stores, Routes and Operations)
  • be built with Opal and Webpack (no Middleman)
  • demonstrate the use of hyperloop-js as a simple alternative deployment method (hyperloop-js coming in via NPM)
  • consist of just three files (index.html, app.js and app.css)
  • have super fast client-side search
  • will use HyperRouter for routing
  • ultra-responsive UI based on SemanticUIReact (we are ditching bootstrap)
  • work online and offline
  • HTTP.get all DOCS pages directly from the gems with client-side markdown
  • have live editing with (hopefully) a Ruby linter and good error messages
  • will be as SEO friendly as the current site (through pre-rendering)
  • be beautiful to behold!

Adding pages and sections

Adding a section

  • Add a route to the Router app/components/router/app_router.rb
  • Add a menu item to app/components/shared/app_menu.rb
  • Create folder in components and add a xxx_page.rb component which will be rendered by the router. See one of the other examples, each folder has three files - xxx_page.rb, xxx_body.rb and xxx_sidebar.rb (assuming your want the three column layout)

Pages (PageBody and PageToc)

Not all sections need to load pages, but if you do then:

  • See the init method in app/stores/site_store, you will need to add a loader which loads the pages an sets a new key in the @section_stores hash
  • Pass the store to PageBody and PageToc and they will redner the Toc and current page and will also handle all navigation and loading of the correct page

Structure

  • There is one singleton Store - SiteStore which contains many instances of SectionStore (one per section)

## Setup and build

Setup

  • bundle
  • npm install
  • npm install [email protected] -g <-- if you don't have Webpack command line

Build

  • To build packs.js and app.js: webpack (-p for production mode)
  • To build app.js: bundle exec rake build

Running the server

We use Rack and OpelHotReloader as a development environment. Website Components are rebuilt by sprockets on server start. You will need to build bundle.js (webpack).

To start the server:

foreman start Browse http://localhost:9292/

Code blocks

Runable code blocks

Code blocks need to render properly in Github and also on the site. Some code blocks are live and runanle.

Normal code block - (three-backticks ruby)

Runable code block - (three-backticks ruby runable)

All runable code blocks must have a Hyperloop Component class Anything < Hyperloop::Component somewhere near the beginning of the code block.