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

dk-bff-server

v3.4.5

Published

Simple Backend-For-Frontend server

Downloads

136

Readme

Simple Backend-For-Frontend server

npm license size

[!WARNING]
It's fine if you use this library from NPM package with a static versioning in case you want it for some pet-project or to test it's capabilities.

But for production use it's strongly recommended to create a fork, because I do not write Changelogs and may break / add some functionality without notice.

Extensible BFF server based on Express that handles static and security.

Features

  • Handles static resources with Brotli/Gzip support (should be generated by bundler)
  • Supports security rules
  • Supports HTTPS (locally) / HTTP protocols
  • Supports async template modifications for SSR
  • Restricts cache for HTML template
  • Can respond with versionIdentifier using GET /get-app-version for notifying users when new version is released
  • Handles 404 errors
  • Gathers performance metrics that could be injected in template

Usage

  1. Create file ex. ./server.ts
import path from 'path';

import { runServer } from 'dk-bff-server';

import { env } from '../env';
import { paths } from '../paths';

void runServer({
  port: env.EXPRESS_PORT, // number
  https: env.HTTPS_BY_NODE, // boolean
  templatePath: path.resolve(paths.build, 'template.html'), // path string
  staticFilesPath: paths.build, // path string
  versionIdentifier: env.GIT_COMMIT, // string
  compressedFilesGenerated: env.GENERATE_COMPRESSED, // boolean
  templateModifier: ({ template }) => {
    return Promise.resolve(
      template
        .replace(
          '<!-- HOST_DEPENDENT_CONFIG -->',
          JSON.stringify({
            API_HOST: env.API_HOST,
            IMAGE_STORAGE_URL: env.IMAGE_STORAGE_URL,
          })
        )
    );
  },
  injectMeasures: ({ template, measures }) =>
    template.replace('<!-- MEASURES -->', JSON.stringify({ server: measures }, null, 2)),
  
  customMiddlewares: [
    (app) => {
      // your middlewares
      // app.use(cookieParser());
    }
  ],

  /**
   * @docs: https://github.com/helmetjs/helmet
   * @docs: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
   */

  helmetOptions: {
    contentSecurityPolicy: {
      directives: {},
    }
  },
});
  1. Build via you bundler
  2. Start using recipe in package.json, ex.
{
  "scripts": {
    "start": "node -r dotenv/config ./build/server.js"
  }
}