Configuration (static.config.js)

A static.config.js file is optional, but recommended at your project root to use react-static to its fullest potential. If present, it must default export an object optionally containing any of the following properties:

getRoutes

An asynchronous function that should resolve an array of route objects. You'll probably want to use this function to request any dynamic data or information that is needed to build all of the routes for your site. It is also passed an object containing a dev boolean indicating whether its being run in a production build or not.

// static.config.js export default { getRoutes: async ({ dev }) => [...routes] }

Awesome Tip: Changes made to static.config.js while the development server is running will automatically run getRoutes again and any changes to routes or routeData will be hot-reloaded instantly! Don't want to edit/resave your config file? Try using reloadRoutes!

route

A route is an object that represents a unique location in your site and is the backbone of every React-Static site.

It supports the following properties:

  • path: String - The path of the URL to match for this route, excluding search parameters and hash fragments, relative to your siteRoot + basePath (if this is a child route, also relative to this route's parent path)
  • component: String - The path of the component to be used to render this route. (Relative to the root of your project)
  • getData: async Function(resolvedRoute, { dev }) => Object - An async function that returns or resolves an object of any necessary data for this route to render.
    • Arguments
    • resolvedRoute: Object - This is the resolved route this function is handling.
    • flags: Object{} - An object of flags and meta information about the build
    • dev: Boolean - Indicates whether you are running a development or production build.
  • is404: Boolean - Set to true to indicate a route as the 404 handler for your site. Only one 404 route should be present in your site!
  • children: Array[Route] - Routes can and should have nested routes when necessary. Route paths are inherited as they are nested, so there is no need to repeat a path prefix in nested routes.
  • redirect: URL - Setting this to a URL will perform the equivalent of a 301 redirect (as much as is possible within a static site) using http-equiv meta tags, canonicals, etc. This will force the page to render only the bare minimum to perform the redirect and nothing else.
  • noindex: Boolean - Set this to true if you do not want this route or its children indexed in your automatically generated sitemap.xml. Defaults to false.
  • permalink: String - You can optionally set this route to have a custom xml sitemap permalink by supplying it here.
  • lastModified: String(YYYY-MM-DD) - A string representing the date when this route was last modified in the format of YYYY-MM-DD.
  • priority: Float - An optional priority for the sitemap.xml. Defaults to 0.5

Example:

// static.config.js export default { getRoutes: async ({ dev }) => [ // A simple route { path: 'about', component: 'src/containers/About' }, // A route with data { path: 'portfolio', component: 'src/containers/Portfolio', getData: async () => ({ portfolio }) }, // A route with data and dynamically generated child routes { path: 'blog', component: 'src/containers/Blog', getData: async () => ({ posts }), children: posts.map(post => ({ path: `post/${post.slug}`, component: 'src/containers/BlogPost', getData: async () => ({ post }) })) }, // A 404 component { is404: true, component: 'src/containers/NotFound' } ] }

getSiteData

getSiteData is very similar to a route's getData function, but its result is made available to the entire site via the SiteData and getSiteData component/HOC. Any data you return here, although loaded once per session, will be embedded in every page that is exported on your site. So tread lightly ;)

Example:

// static.config.js export default { getSiteData: async ({ dev }) => ({ title: 'My Awesome Website', lastBuilt: Date.now() }) }

siteRoot

Your siteRoot in the format of protocol://domain.com is highly recommended and is necessary for many things related to SEO to function for your site. So far, this includes:

  • Automatically generating a sitemap.xml on export
  • Forcing absolute URLs in statically rendered links.
    Make sure that you include https if you serve your site with it (which we highly recommend). Any trailing slashes including the pathname will be removed automatically. If you need to set a base path for your site (eg. if you're using github pages), you'll want to use the basePath option.

Example:

// static.config.js export default { siteRoot: 'https://mysite.com' }

stagingSiteRoot

Works exactly like siteRoot, but only when building with the --staging build flag.

basePath

Your basePath in the format of some/route is necessary if you intend on hosting your app from a specific route on your domain (eg. When using Github Pages or for example: https://mysite.com/blog where blog would the basePath)
All leading and trailing slashes are removed automatically.

Example:

// static.config.js export default { basePath: 'blog' }

stagingBasePath

Works exactly like basePath, but only when building with the --staging build flag.

devBasePath

Works exactly like basePath, but only when running the dev server.

extractCssChunks

extractCssChunks replaces default ExtractTextPlugin with ExtractCssChunks. It enables automatic CSS splitting into separate files by routes as well as dynamic components (using react-universal-component). More information about the plugin and why it is useful as a part of CSS delivery optimisation. Defaults to false.

inlineCss

By using extractCssChunks option and putting code splitting at appropriate places, your page related CSS file can be minimal. This option allows you to inline your page related CSS in order to speed up your application by reducing the number of requests required for a first paint. Default to false.

Document

It's never been easier to customize the root document of your website! Document is an optional (and again, recommended) react component responsible for rendering the root of your website.

Things you may want to place here:

  • Custom head and/or meta tags
  • Site-wide analytics scripts
  • Site-wide stylesheets

Props

  • Html: ReactComponent - Required - An enhanced version of the default html tag.
  • Head: ReactComponent - Required - An enhanced version of the default head tag.
  • Body: ReactComponent - Required - An enhanced version of the default body tag.
  • children: ReactComponent - Required - The main content of your site, including layout, routes, etc.
  • routeInfo: Object - All of the current route's information, including any routeData.
  • siteData: Object - Any data optionally resolved via the getSiteData function in this config file.
  • renderMeta: Object - Any data optionally provided via the renderToHtml function in this config file.
// static.config.js export default { Document: ({ Html, Head, Body, children, siteData, renderMeta }) => ( <Html lang="en-US"> <Head> <meta charSet="UTF-8" /> <meta name="viewport" content="width=device-width, initial-scale=1" /> </Head> <Body>{children}</Body> </Html> ) }

webpack

An optional function or array of functions to transform the default React-Static webpack config. Each function will receive the previous webpack config, and expect a modified or new config to be returned. You may also return a "falsey" or undefined value if you do not want to modify the config at all.

Function Signature

webpack: []Function( previousConfig, args: { stage, defaultLoaders: { jsLoader, cssLoader, fileLoader } } ) => { return newConfig // or a falsey value to cancel transformation }
  • The webpack property's value can be an array of functions or a single function.
  • Each function will receive the previous webpack config, and can return a modified or new config.
  • Return any falsey value to cancel the transformation
  • args.stage is a string of either prod, dev or node, denoting which stage react-static is building for.
  • args.defaultLoaders - A convenience object containing the default react-static webpack rule functions:
    • jsLoader - The default loader for all .js files (uses babel)
    • cssLoader - The default style loader that supports importing .css files and usage of css modules.
    • fileLoader - The default catch-all loader for any other file that isn't a .js .json or .html file. Uses url-loader and file-loader

When webpack is passed an array of functions, they are applied in order from top to bottom and are each expected to return a new or modified config to use. They can also return a falsey value to opt out of the transformation and defer to the next function.

By default, React Static's webpack toolchain compiles .js and .css files. Any other file that is not a .js .json or .html file is also processed with the fileLoader (images, fonts, etc.) and will move to ./dist directory on build. The source for all default loaders can be found in react-static/lib/webpack/rules/.

Our default loaders are organized like so:

const webpackConfig = { ... module: { rules: [{ oneOf: [ jsLoader, // Compiles all .js files with babel cssLoader, // Supports basic css imports and css modules fileLoader // Catch-all url-loader/file-loader for anything else }] } ... }

Note: Usage of the oneOf rule is not required, but recommended. This ensures each file is only handled by the first loader it matches, and not any loader. This also makes it easier to reutilize the default loaders, without having to fuss with excludes. Here are some examples of how to replace and modify the default loaders:

Replacing all rules

// static.config.js export default { webpack: config => { config.module.rules = [ // Your own rules here... ] return config } }

Replacing a default loader for a different one

// static.config.js export default { webpack: (config, { defaultLoaders }) => { config.module.rules = [{ oneOf: [ defaultLoaders.jsLoader, { // Use this special loader // instead of the cssLoader } defaultLoaders.fileLoader, ] }] return config } }

Adding a plugin

// static.config.js import AwesomeWebpackPlugin from 'awesome-webpack-plugin' export default { webpack: config => { config.plugins.push(new AwesomeWebpackPlugin()) return config } }

Using multiple transformers

// static.config.js export default { webpack: [ (config, { defaultLoaders }) => { config.module.rules = [ { oneOf: [ defaultLoaders.jsLoader, defaultLoaders.cssLoader, { loader: 'file-loader', test: /\.(fancyFileExtension)$/, query: { limit: 10000, name: 'static/[name].[hash:8].[ext]' } }, defaultLoaders.fileLoader ] } ] return config }, config => { console.log(config.module.rules) // Log out the final set of rules } ] }

devServer

An Object of options to be passed to the underlying webpack-dev-server instance used for development.

Example:

// static.config.js export default { // An optional object for customizing the options for the devServer: { port: 3000, host: '127.0.0.1' } }

renderToHtml

An optional function that can be used to customize the static rendering logic.

  • Arguments
    • render: Function: A function that renders a react component to an html string
    • Component: the final react component for your site that needs to be rendered to an HTML
    • meta, a mutable object that is exposed to the optional Document component as a prop
    • webpackStats, the webpack stats generated from the "prod" stage
  • Returns an HTML string to be rendered into your Document component provided in your config (or the default one).

This also happens to be the perfect place for css-in-js integration (see [styled-components] and [glamorous] examples for more information)

Example:

// static.config.js export default { renderToHtml: async (render, Component, meta, webpackStats) => { // Add meta you may want meta.hello = 'world' // Use any custom rendering logic return render(<Component />) } }

paths

An object of internal directories used by react-static that can be customized. Each path is relative to your project root and defaults to:

// static.config.js export default { paths: { root: process.cwd(), // The root of your project. Don't change this unless you know what you're doing. src: 'src', // The source directory. Must include an index.js entry file. dist: 'dist', // The production output directory. devDist: 'tmp/dev-server', // The development scratch directory. public: 'public' // The public directory (files copied to dist during build) } }

onStart

A utility function that runs when the dev server starts up successfully. It provides you with the final, readonly devServer config object for your convenience.

Example:

// static.config.js export default { onStart: ({ devServerConfig }) => { console.log('The dev server is working!') } }

onBuild

A utility function that runs when the a build completes successfully.

Example:

// static.config.js export default { onBuild: async () => { console.log('Everything is done building!') } }

bundleAnalyzer

An optional Boolean. Set to true to serve the bundle analyzer on a production build.

// static.config.js export default { bundleAnalyzer: true }

outputFileRate

An optional Int. The maximum number of files that can be concurrently written to disk during the build process.

// static.config.js export default { outputFileRate: 100 }

prefetchRate

An optional Int. The maximum number of inflight requests for preloading route data on the client.

// static.config.js export default { prefetchRate: 10 }

disableRouteInfoWarning

An optional Boolean. Set to true to disable warnings during development when routeInfo.json is not found for a specific route. Useful if you are using custom routing!

// static.config.js export default { disableRouteInfoWarning: true }