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

set-status

v0.0.1

Published

Set a custom HTTP status code for the client by utilizing proxy and a meta tag.

Downloads

6

Readme

set-status

Set a custom HTTP status code for the client by utilizing proxy and a meta tag.

Note: Manipulating HTTP status code is not recommended for production. Use at your own risk.

Install

pnpm add set-status

Configuration

You can configure all settings with the environment variables.

  • Set the TARGET_URL as your target app URL, http://localhost:3000 by default.
  • Set the PROXY_SERVER_PORT for the proxy server port, 3001 by default.
  • Set the TARGET_META_NAME for the target meta tag, set-status by default.
  • Set the IGNORE_PATH_REGEX for the regex to ignore the target path set to Next.js by default.

See .env.example for an example.

Usage

Basic

Run the proxy server with the following command:

pnpm proxy-status

The proxy server will look for the target meta tag and set the status code to the client.

<meta name="set-status" content="401" />

The meta tag above will let the proxy server set the status code to 401.

Recommended

Install concurrently to run the proxy server and your production app concurrently.

pnpm add concurrently

Set your start script in package.json as follows:

{
  "scripts": {
    "start": "concurrently \"pnpm proxy-status\" \"YOUR PRODUCTION COMMAND\""
  }
}
pnpm start

Next.js

See examples in examples/nextjs.

In Next.js, you can statically set a custom meta tag by using a Metadata API.

Through this, we can set the status code read from the target meta tag.

// page.tsx

export default function Unauthorized() {
  return (
    <div>
      <h1>401</h1>
      <p>Unauthorized</p>
    </div>
  )
}

export const metadata = {
  other: {
    'set-status': 401,
  },
}

Also, you can dynamically set the target meta tag by using generateMetadata function.

// page.tsx

export async function generateMetadata() {
  const res = await fetch('https://example.com/api')
  
  if (res.status !== 200) {
    return {
      other: {
        'set-status': res.status,
      },
    }
  }
}

For more information about the Metadata API, see the Next.js documentation.