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

hyper-express-route-path

v1.0.1

Published

A small module that helps extract the path of a certain route in hyper-express.

Downloads

11

Readme

hyper-express-route-path

This is a tiny module that uses path-match to determine the exact path extracted from a route.

This was built to work with hyper-express and I use it to help manage static file serving.

Ah! Oh! What does it do?

Say you have the route /assets/* to server your assets, and you try to access the file /assets/vids/1.mp4, it calculates the route path to be /vids/1.mp4 so you can look for that file in your static directory.

Why this is important is because static files will effectively be served off many routes and you will need a way to map to them.

Usage

You can use this as a middleware or within the route.

const HyperExpress = require('hyper-express');
const webserver = new HyperExpress.Server();

// require module
const heRoutePath = require('hyper-express-route-path');

// to use it as a middleware
webserver.use(heRoutePath.middleWare);

// Create GET route to serve 'Hello World'
webserver.get('/*', async (request, response) => {

	// Now every request object will have a new property; routePath
	response.send(request.routePath);
	// => '/vids/1.mp4' when accessing /vids/1.mp4

	//You can also use it within a route as follows
	let filePath = heRoutePath.routePath(request);
	// Of course we probably don't need this as we have already used it as a middleware ;)
	response.send(filePath);
	// => '/vids/1.mp4' when accessing /vids/1.mp4

});

// Activate webserver by calling .listen(port, callback);
webserver
	.listen(80)
	.then((socket) => console.log('Webserver started on port 80'))
	.catch((error) => console.log('Failed to start webserver on port 80'));