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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@awesomeness-js/server

v1.1.20

Published

Awesomeness Multi-Site Server

Readme

Awesomeness JS Configuration

Most configurations for Awesomeness JS are done through the .awesomeness/config.js file.

The ./awesomeness/ folder and you can customize the location by modifying the import paths in package.json.

For an Example Application see the repo

@awesomeness-js/app-template

Underlying Request Flow

Pre Routing

  • start
  • attachAwesomenessRequest
    • gets awesomenessRequest.awesomenessType [page, api, generic]
  • staticFiles
  • beforeRouteMiddleware
  • routeRequest

Routing

  • needs to be valid route for [page, api]
    • /[^a-zA-Z0-9/_-]/ -> make sure there is no dots in the path -> 404

API Routing ( needs awesomenessType in post body api)

  • try /api/routes/${awesomenessRequest.pageRoute}
    • try site specific first
    • then try common routes (needs to be edited uses URL and not passed config)
  • validateRequest
  • route index.js

Page Routing ( needs awesomenessType in post body page)

  • pageInfo
  • validateRequest
  • fetchPage
  • finalFormat

Generic Routing ( has no defined awesomenessType in post body)

  • method must be get or 405 is thrown
  • /test -> returns awesomeness is working
  • routes to staticFiles
  • awesomenessRequest.awesomenessType is not set in POST body
  • request is treated as a static file request
  • static file served is it exists in the public folder
    • site specific first
    • then common files

If a public static file is not found

  • public/index.html is served
  • You DO NOT need your own public/index.html file
    • The awesomeness-ui framework provides a default one
    • this calls app.init()

From the Browser

What happens

  1. User visits a page
  • Server receives request

Static Files

index.html

License

This project is licensed under the Apache License 2.0.

© 2026 Your Name. All rights reserved.