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-https

v1.1.16

Published

This is a simple HTTPS proxy to be used with Next.js in local development.

Downloads

1,050

Readme

next-https

This is a simple HTTPS proxy to be used with Next.js in local development.

Motivation

A secure HTTP connection is necessary when interfacing with certain Web APIs restricted to secure contexts. This package simply starts an HTTP proxy pointing at your Next.js server instance to simplify local development.

Getting Started

Install the package

yarn add next-https

Inside your Next.js configuration file:

// next.config.js
const useHttps = require("next-https");

// You can pass options here
const withHttps = useHttps({
  enabled: process.env.NODE_ENV === "development",
});

// pass your Next.js options here
module.exports = withHttps({
  reactStrictMode: true,
});

NOTE: When using the default configuration options, you'll have to accept the self-signed certificate the first time you access the page. This is safe to do in a local development environment only.

Configuration

You can use next-https with default configuration options.

| name | required | description | | --------- | -------- | ------------------------------------------------------------- | | enabled | no | Defaults to process.env.NODE_ENV === 'development' | | host | no | Next.js server hostname, defaults to localhost | | target | no | Next.js port target, defaults to 3000 | | key | no | Path to the key, defaults to this package's key file | | cert | no | Path to the certificate, defaults to this package's cert file |

Using custom certificates

If you want to use a custom domain name or to remove the initial warning from your browser, you'll need to setup your own certificates.

To avoid the warnings you need to install the local root CA in your computer in order for your browser to trust the certificates.

For this you can use mkcert

brew install mkcert

Install the local CA

mkcert -install

Create the certificate files

mkcert example.com "*.example.com" example.test localhost 127.0.0.1 ::1

And pass your custom certificate and key

// next.config.js
const nextHttps = require("next-https");

// You can pass options here
const withHttps = nextHttps({
  host: "example.com",
  key: './path/to/example-key.pem'),
  cert: './path/to/example-cert.pem'),
});

// pass your Next.js options here
module.exports = withHttps({
  reactStrictMode: true,
});