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

roads-starter

v2.3.1

Published

A starter project for building websites with roads and roads-api

Downloads

10

Readme

roads-starter

Getting Started

Trying the example

  1. Pop open the config folder and make duplicates of every file in there. Remove the word "example" from the copies.
  2. In each of those new non-example files, fill in the appropriate values.
  3. From the example folder run ./docker-compose.sh up to test the example

Building a new project

  1. Copy the contents of the example folder to a new project
  2. Create a package.json file with a dependency on roads-starter (remember to make it private if you need to!)
  3. Update all ../index.js references (such as the one in server.js) to reference roads-starter
  4. Pop open the config folder and make duplicates of every file in there. Remove the word "example" from the copies.
  5. In each of those new non-example files, fill in the appropriate values.
  6. Run ./docker-compose.sh up to test the copied example
  7. Add new API routes in the API folder and reference them via server.js.
  8. Add new web routes in the privateRoutes.js (for routes that access private data or endpoints) or publicRoutes.js (for routes that can safely be sent to the client and executed in the browser)