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

guidepost

v1.0.0

Published

Redirect all requests to another domain Redirect all requests to another domain

Downloads

5

Readme

guidepost Build Status

Redirect all requests to another domain

Installation

npm install --save guidepost

Usage

const guidepost = require('guidepost');

const app = guidepost('https://google.com')
app.listen(80);

All requests coming into port 80 will be redirected to https://google.com, preserving the URL path.

Why?

This redirector returns an express app, so you can pass it to http.createServer() or https.createServer(). This way you have full control over ports, SSL certificates, adding routing and middleware, but still need very little configuration!

Advanced Examples

HTTPS server using https.createServer():

const https = require('https');
const guidepost = require('guidepost');

const app = guidepost('https://google.com');
https.createServer({
	key: fs.readFileSync('test/fixtures/keys/agent2-key.pem'),
	cert: fs.readFileSync('test/fixtures/keys/agent2-cert.pem')
}, app).listen(80);

Make an exception to redirecting:

const app = guidepost('https://google.com');
app.get('/test', (request, response) => {
	response.end('No redirect!');
});
app.listen(80);
// '/test' ==> 'http://localhost:80/test'
// '/test2' ==> 'https://google.com/test2' 

Log all requests:

const app = guidepost('https://google.com');
app.use((request, response, next) => {
	console.log(`${request.url} was requested`);
	next();
});
app.listen(80)

How does it work?

guidepost uses a ES6 proxy to only add the redirect handler at the very end of the express router. This is why you can add middleware after you have called guidepost().

Support

Only node >= 6.0.0 is supported because the module makes use of proxies.

License

ISC @ Jonny Burger