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

next-multisite

v0.1.0

Published

This package wraps around `next`, allowing you to host multiple domains from one project.

Downloads

3

Readme

next-multisite

This package wraps around next, allowing you to host multiple domains from one project.

Usage

For a complete example, see the example folder.

Installation

Install next-multisite instead of installing next

npm install next-multisite

Folder structure

next-multisite uses the following folder structure to serve multiple sites. Sites are selected by the first part of the domain name, so in this example site1.example.com and site2.example.com would be served correctly.

sites
  /site1
    /pages
      /page.js
      /other-page.js
  /site2
    /pages
      /page.js
      /other-page.js

Running next-muultisite

Run next-multisite for both development and production build. If the NODE_ENV variable is set to production, next build output is used.

"scripts": {
    "dev": "next-multisite",
    "build": "next build",
    "start": "cross-env NODE_ENV=production next-multisite"
}

Accessing sites locally

By default, domains ending in .localhost will all map to your local machine. Thus, you can easily open your different sites by going to http://site1.localhost:3000/, http://site2.localhost:3000/, etc.. When starting the process, these urls will be printed automatically.