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

force-domain

v0.1.0

Published

Use the provided domain. Useful when managing more than one

Downloads

4

Readme

force-domain

A module part of the project Clean Url. It forces a domain, for those who manage multiple domains. Say you have the following domains:

  • example.info
  • example.com
  • example.org

But you want them all to use the last one, example.org. Easy, just point them all to the same server and let force-domain to take care of it. It's also useful when changing domains, since urls will be preserved: example.info/any/folder will redirect to example.org/any/folder

Use it with your middleware:

// Include the repository from npm
var forcedomain = require('force-domain')({ host: "example.org" });

// Allow express to use it (put this before your routes!)
app.use(notrailing);

Options

There are some options that can be used with the module:

  • host: the domain that you want to use. You can also use this to force www., but we don't really recommend it
  • localhost: defaults to true. Allow for localhost to be excluded for development purposes.
  • permanent: defaults to true.

Testing

npm test should do the trick to make sure everything works

Known issues

If you are behind a proxy like in heroku, when there's a redirect from force-domain it will redirect to the http version. We recommend using force-https or the full clean-url npm modules to avoid this.