@fastly/compute-js-static-publish

Static Publisher for JavaScript on Compute@Edge

Using a static site generator to build your website? Do you simply need to serve some static files? With compute-js-static-publish, now you can deploy and serve everything from Fastly's blazing-fast Compute@Edge.

How it works

You have some HTML files, along with some accompanying CSS, JavaScript, image, and font files in a directory. Perhaps you've used a framework or static site generator to build these files.

Assuming the root of your output directory is ./public,

1. Run compute-js-static-publish

npx @fastly/compute-js-static-publish@latest --public-dir=./public

This will generate a Compute@Edge application at ./compute-js. It will add a default ./src/index.js file that serves the static files from your project.

2. Test your application using Fastly's local development server

cd ./compute-js
npm install
fastly compute serve

The build process will generate a /src/statics.js file (in ./compute-js) that holds references to your project's public files.

3. When you're ready to go live, deploy your Compute@Edge service

fastly compute publish

Each time you build your Compute@Edge project (by running fastly compute serve or fastly compute publish), compute-js-static-publish will scan your ./public directory and regenerate /src/statics.js.

You can modify /src/index.js to suit your needs, such as adding your own API endpoints. This file will not be overwritten after it is created.

CLI options

Most arguments are optional, and if provided, override the defaults described below.

npx @fastly/compute-js-static-publish \
    --public-dir=./build \
    --static-dir=./build/static \
    --output=./compute-js \
    --spa=./build/index.html

Any configuration options will be written to a static-publish.rc.js file.

Option	Default	Description
preset	(None)	Apply default options from a specified preset. See "Frameworks and Static Site Generators".
output	./compute-js	The directory in which to create the Compute@Edge application.
public-dir	(None)	Required. The root of the directory that contains your website's public files. Files at this path will be served by the generated Compute@Edge application.
static-dir	(None)	A subdirectory of --public-dir that contains the website's static assets. Files at this path will be cached by the browser for 1 year. Use versioned or hashed filenames to avoid serving stale assets.
auto-index	index.html,index.htm	Handle request paths that end in / by appending these names (comma-separated), in the specified order. By default, if /path/to/a/ is requested, attempt to serve /path/to/a/index.html, then /path/to/a/index.htm.
auto-ext	.html,.htm	Handle request paths that do not end in / by appending these extensions (comma-separated), in the specified order. By default, if /path/to/a is requested, attempt to serve /path/to/a, /path/to/a.html, then /path/to/a.htm.
spa	(None)	Serve this file when the request path does not match known paths – with a 200 status code. Useful for apps that use client-side routing.
not-found-page	<public-dir>/404.html	Serve this file when the request path does not match known paths – with a 404 status code. Useful for a custom 404 error page.

On subsequent builds of your Compute@Edge application, compute-js-static-publish will run with a special flag, build-static, reading from stored configuration, then scanning the --public-dir directory to recreate ./src/statics.js.

Fastly service options

These arguments are used to populate the fastly.toml and package.json files of your Compute@Edge application.

Option	Default	Description
name	name from package.json, or compute-js-static-site	The name of your Compute@Edge application.
description	description from package.json, or Compute@Edge static site	The description of your Compute@Edge application.
author	author from package.json, or [e-mail]	The author of your Compute@Edge application.
service-id	(None)	The ID of an existing Fastly WASM service for your Compute@Edge application.

Usage with frameworks and static site generators

compute-js-static-publish supports preset defaults for a number of frameworks and static site generators:

--preset	--public-dir	--static-dir	Notes
cra (or create-react-app)	./build	./build/static	For apps written using Create React App. Checks for a dependency on react-scripts.
cra-eject	./build	./build/static	For apps written using Create React App, but which have since been ejected via npm run eject. Does not check for react-scripts.
vite	./dist	(None)	For apps written using Vite.
sveltekit	./dist	(None)	For apps written using SvelteKit.
next	./out	(None)	For apps written using Next.js, using npm run export. *1
gatsby	./public	(None)	For apps written using Gatsby.
docusaurus	./build	(None)	For apps written using Docusaurus

You may still override any of these options individually.

*1 - For Next.js, consider using @fastly/next-compute-js, a Next.js server implementation that allows you to run your Next.js application on Compute@Edge.

Troubleshooting

If you're using Fastly CLI 4.0.0 or newer, and your project was scaffolded using a version of this tool older than 2.1.0, then you'll need to either re-scaffold your project, or add the following to the fastly.toml file that is in your compute-js directory.

[scripts]
  build = "npx @fastly/compute-js-static-publish --build-static && npx webpack && npx js-compute-runtime ./bin/index.js ./bin/main.wasm"

If Fastly CLI has already added build = "npx webpack && npx js-compute-runtime ./bin/index.js ./bin/main.wasm", then replace it with the above.

Issues

If you encounter any non-security-related bug or unexpected behavior, please file an issue.

Security issues

Please see our SECURITY.md for guidance on reporting security-related issues.

License

MIT.