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

@lightspeed/express-csp-middleware

v1.0.2

Published

Common content security policy headers Express middleware for Lightspeed apps

Downloads

46

Readme

@lightspeed/express-csp-middleware

npm version

Introduction

Express middleware for generating the HTTP Content-Security-Policy header for Lightspeed apps, allowing developers to control resources the user agent is allowed to load for a given page.

Quick Start

  1. Install the dependency in your webapp.
yarn add @lightspeed/express-csp-middleware
  1. Apply the middleware to your Express server.
// server.ts
import express from 'express';
import { cspMiddleware } from '@lightspeed/express-csp-middleware';

const app = express();
app.use(cspMiddleware({ env: process.env.NODE_CONFIG_ENV }));
  1. Script tags from HTML returned from the server must be attributed with the same unique nonce for the given request. For example, in a Next.js app with serverside rendering, apply the nonce as follows:
// app/_document.tsx
import React from 'react';
import Document, { Head, Main, NextScript, NextDocumentContext } from 'next/document';

type MyDocumentProps = {
  nonce: string;
};

export default class MyDocument extends Document<MyDocumentProps> {
  static async getInitialProps(ctx: NextDocumentContext) {
    const { nonce } = (ctx.res as any).locals;
    const initialProps = await Document.getInitialProps(ctx);
    return { ...initialProps, nonce };
  }

  render() {
    return (
      <html>
        <Head nonce={this.props.nonce}>
          <title>Lightspeed Retail - Cool Page</title>
        </Head>
        <body>
          <Main />
          <NextScript nonce={this.props.nonce} />
        </body>
      </html>
    );
  }
}
  1. Update all pages to include a getInitialProps method on the component. This will override nextjs to force server-side rendering and provide access to req and res in _document. You can read more here
// pages/index.tsx
import * as React from 'react';

const Hello = () => {
  return <div>Hello World!</div>;
};

Hello.getInitialProps = async () => ({});

Customizing your own presets

It is possible to customize the CSP middleware policies.

You may pass in an object into the additionalPresets keys. These values will either replace the existing presets or create a new entity.

In order for them to be configured properly, please ensure that the key's match and that the value is an array of strings.

The default values used by the CSP middleware are exported to faciliate extending the defaults rather than replacing them.

import { cspMiddleware, imgSrc } from '@lightspeed/express-csp-middleware';

const myExtraPresets = {
  'img-src': imgSrc.concat(['"cdn-a"', '"cdn-b"']),
  'connect-src': ['"http:"'],
};

app.use(cspMiddleware({ env: process.env.NODE_CONFIG_ENV, additionalPresets: myExtraPresets }));