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

now-test-route

v0.0.5

Published

A CLI to test if a URL path will match a route, a builder and a file based on a now.json file and a file system state

Downloads

8

Readme

now-test-route

A CLI to test if a URL path will match a route, a builder and a file based on a now.json v2 file and a file system state.

Install

npm i -g now-test-route

Usage

now-test-route <route> [--config {nowJson}]
  • <route> - The route you want to test. Examples /img/logo.png or POST /submit.
  • nowJson - (optional) The path to the now.json file with your config. If no path is provided, the now.json file will be looked up in the current directory.

Examples

Consider the following file system structure:

➜  wedding git:(route-playground) ✗ tree -I node_modules
.
├── app.yaml
├── google.js
├── index.js
├── now.json
├── package-lock.json
├── package.json
├── static
│   ├── fonts
│   │   └── amarillo.otf
│   ├── img
│   │   ├── couple.jpg
│   ├── index.html
│   ├── scripts
│   │   ├── main.js
│   │   └── vendor.js
│   └── styles
│       ├── styles.css

And this now.json file:

➜  wedding git:(route-playground) ✗ cat now.json 
{
    "version": 2,
    "name": "Wedding",
    "builds": [
        { "src": "./static/*/*", "use": "@now/static" },
        { "src": "./static/index.html", "use": "@now/static" },
        { "src": "./index.js", "use": "@now/node-server" }
    ],
    "routes": [
        { "src": "/", "dest": "/static/index.html" },
        { "src": "/(img|fonts|scripts|styles)/(.*)", "dest": "/static/$1/$2" },
        { "src": "/submit", "methods": ["POST"], "dest": "index.js" }
    ],
    "regions": ["gru", "sfo1"]
}

index.html

Test getting what / is routed to:

➜  wedding git:(route-playground) ✗ now-test-route /
SUCCESS: 
      matched input route / 
      to file /static/index.html 
      with builder @now/static

/submit

Test what POST /submit is routed to:

➜  wedding git:(route-playground) ✗ now-test-route POST /submit
SUCCESS: 
      matched input route POST /submit 
      to file index.js 
      with builder @now/node-server

License

MIT