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

@fab/plugin-render-html

v1.0.0-rc.9

Published

Module to render static HTML files with FAB injections

Downloads

117

Readme

@fab/plugin-render-html

A plugin for serving static HTML files with FAB_SETTINGS injected

Rationale

Static HTML is a big part of modern frontend applications—whether you're serving all routes as a single page application to a single index.html or pre-rendering dozens or hundreds of routes, generating static HTML gives you a bulletproof deploy artifact.

In the FAB ecosystem, however, we want the ability for a compiled FAB to be linked against multiple environments, and so a build-time static HTML file isn't going to work. This module solves that.

Usage

{
  plugins: {
    // ...
    '@fab/plugin-render-html': {
      // Can be left blank. See below for config options
    },
    // ...
  },
}

Configuration

By default, this module has the following options:

{
  'match-html': '/.html$/i', // path to match for HTML files
  injections: {
    // if not specified, injects only the following module
    env: {
      name: 'FAB_SETTINGS', // which global variable to use?
    },
  },
  fallback: '/index.html', // Which HTML file to use for all routes
  inline: 'fallback-only', // Which HTML files to inline into server.js
}

Injections

@fab/plugin-render-html works by compiling your HTML files into a template (atm we use Mustache but not for any particular reason, it just works), which means that the static HTML files can be dynamically enriched on the server.

Most commonly, this will inject the following <script> tag into any HTML response as it's being streamed to the client:

<!DOCTYPE html>
<html lang="en">
  <head>
    <script type="text/javascript">
      window.FAB_SETTINGS = {
        ENV_VAR_NAME: 'env var value',
      }
    </script>
    <!-- ... -->
  </head>
  <!-- ... -->
</html>

Your client-side JS can then import the global FAB_SETTINGS object to rewire API requests, etc.

Fallback

👉 Valid options are string | true | false.

  • false means don't render a fallback, allow 404s to fall through.
  • string is the path to the fallback to use (e.g. /index.html, /200.html)
  • true (default) is equivalent to fallback: '/index.html'

Inline

👉 Valid options are 'fallback-only' | true | false

This module compiles HTML files to a Mustache partially-rendered templates. These can either be inlined into the server.js file for performance or rendered out to _assets files to be stored alongside any other objects in the FAB. This is particularly important for hosting platforms like Cloudflare Workers which have a default worker limit (i.e. max size of server.js) of 1MB.

  • false means save all HTML templates to _assets (safest for large sites)
  • true means inline all HTML templates to server.js (fastest for small sites)
  • 'fallback-only' means only inline the fallback file (safe, and fastest for SPA-style apps)