Github url

razzle

by jaredpalmer

jaredpalmer /razzle

✨ Create server-rendered universal JavaScript applications with no configuration

9.3K Stars 810 Forks Last release: 13 days ago (v3.1.6) MIT License 794 Commits 81 Releases

Available items

No Items, yet!

The developer of this repository has not created any items for sale yet. Need a bug fixed? Help with integration? A different license? Create a request here:

repo-banner

CircleCI Razzle-status npm version Known Vulnerabilities Greenkeeper badge Join the community on Spectrum

Universal JavaScript applications are tough to setup. Either you buy into a framework like Next.js or react-server, fork a boilerplate, or set things up yourself. Aiming to fill this void, Razzle is a tool that abstracts all complex configuration needed for SSR into a single dependency--giving you the awesome developer experience of create-react-app, but then leaving the rest of your app's architectural decisions about frameworks, routing, and data fetching up to you. With this approach, Razzle not only works with React, but also Reason, Elm, Vue, Angular, and most importantly......whatever comes next.

Razzle comes with the "battery-pack included":

  • :fire: Universal Hot Module Replacement, so both the client and server update whenever you make edits. No annoying restarts necessary
  • Comes with your favorite ES6 JavaScript goodies (through
    babel-preset-razzle
    )
  • Comes with the same CSS setup as create-react-app
  • Works with React, Preact, Elm, Reason-React, Inferno, and Rax as well as Angular and Vue if that's your thing
  • Escape hatches for customization via
    .babelrc
    and
    razzle.config.js
  • Jest test runner setup with sensible defaults via
    razzle test
  • :rocket: SPA mode, build client side apps with razzle

Quick Start

npx create-razzle-app my-app cd my-app npm start

Then open http://localhost:3000/ to see your app. Your console should look like this:

Razzle Development Mode

That's it. You don't need to worry about setting up multiple webpack configs or other build tools. Just start editing

src/App.js

and go!

Below is a list of commands you will probably find useful.

npm start

or

yarn start

Runs the project in development mode.
You can view your application at

http://localhost:3000

The page will reload if you make edits.

npm run build

or

yarn build

Builds the app for production to the build folder.

The build is minified and the filenames include the hashes. Your app is ready to be deployed!

npm run start:prod

or

yarn start:prod

Runs the compiled app in production.

You can again view your application at

http://localhost:3000

npm test

or

yarn test

Runs the test watcher (Jest) in an interactive mode. By default, runs tests related to files changed since the last commit.

npm start -- --inspect=[host:port]

or

yarn start -- --inspect=[host:port]

To debug the node server, you can use

razzle start --inspect

. This will start the node server and enable the inspector agent. The

=[host:port]

is optional and defaults to

=127.0.0.1:9229

. For more information, see this.

npm start -- --inspect-brk=[host:port]

or

yarn start -- --inspect-brk=[host:port]

This is the same as --inspect, but will also break before user code starts. (to give a debugger time to attach before early code runs) For more information, see this.

rs

If your application is running, and you need to manually restart your server, you do not need to completely kill and rebundle your application. Instead you can just type

rs

and press enter in terminal.

Razzle Hot Restart

In addition to universal/isomorphic appplications, Razzle can build single page (or client-only) applications. To do this, you can remove

index.js

and

server.js

then

index.html

file inside public folder at the end pass

--type=spa

to your

package.json

's scripts like so:

"scripts": { - "start": "razzle start", + "start": "razzle start --type=spa", - "build": "razzle build", + "build": "razzle build --type=spa", "test": "razzle test --env=jsdom", - "start:prod": "NODE\_ENV=production node build/server.js" + "start:prod": "serve -s build/public" }

Customization

Plugins

As of Razzle 2.0, you can add your plugins to modify your setup.

Using Plugins

You can use Razzle plugins by installing in your project and adding them to your

razzle.config.js

. See the README.md of the specific plugin, but generally speaking, the flow is something like...

yarn add razzle-plugin-xxxx
//./razzle.config.js module.exports = { plugins: ['xxxx'], };

Writing Plugins

Plugins are simply functions that modify and return Razzle's webpack config.

'use strict'; module.exports = function myRazzlePlugin(config, env, webpack, options) { const { target, dev } = env; if (target === 'web') { // client only } if (target === 'node') { // server only } if (dev) { // dev only } else { // prod only } // Do some stuff... return webpackConfig; };

Customizing Babel Config

Razzle comes with most of ES6 stuff you need. However, if you want to add your own babel transformations, just add a

.babelrc

file to the root of your project.

{ "presets": ["razzle/babel", // NEEDED "stage-0"], "plugins": [// additional plugins] }

A word of advice: the

.babelrc

file will replace the internal razzle babelrc template. You must include at the very minimum the default razzle/babel preset.

Extending Webpack

You can also extend the underlying webpack config. Create a file called

razzle.config.js

in your project's root.

// razzle.config.js module.exports = { modify: (config, { target, dev }, webpack) =\> { // do something to config return config; }, };

A word of advice:

razzle.config.js

is an escape hatch. However, since it's just JavaScript, you can and should publish your

modify

function to npm to make it reusable across your projects. For example, imagine you added some custom webpack loaders and published it as a package to npm as

my-razzle-modifictions

. You could then write your

razzle.config.js

like so:

// razzle.config.js const modify = require('my-razzle-modifictions'); module.exports = { modify }

Last but not least, if you find yourself needing a more customized setup, Razzle is very forkable. There is one webpack configuration factory that is 300 lines of code, and 4 scripts (

build

,

start

,

test

, and

init

). The paths setup is shamelessly taken from create-react-app, and the rest of the code related to logging.

CSS Modules

Razzle supports CSS Modules using Webpack's css-loader. Simply import your CSS file with the extension

.module.css

and Razzle will process the file using

css-loader

.

import React from 'react'; import styles from './style.module.css'; const Component = () =\> 

; export default Component;

Polyfills

Polyfills for IE 9, IE 10, and IE 11 are no longer included by default (but you can opt in!) We have dropped default support for Internet Explorer 9, 10, and 11. If you still need to support these browsers, follow the instructions below.

First, install

react-app-polyfill

:

npm install react-app-polyfill

or

yarn add react-app-polyfill

Next, place one of the following lines at the very top of

src/client.js:
import 'react-app-polyfill/ie9'; // For IE 9-11 support import 'react-app-polyfill/ie11'; // For IE 11 support

Environment Variables

Build-time Variables

The following environment variables are embedded during the build time.

  • process.env.RAZZLE\_PUBLIC\_DIR
    : Absolute path to the public directory in the server's filesystem.
  • process.env.RAZZLE\_CHUNKS\_MANIFEST
    : Path to a file containing compiled chunk outputs
  • process.env.RAZZLE\_ASSETS\_MANIFEST
    : Path to a file containing compiled asset outputs
  • process.env.REACT\_BUNDLE\_PATH
    : Relative path to where React will be bundled during development. Unless you are modifying the output path of your webpack config, you can safely ignore this. This path is used by
    react-error-overlay
    and webpack to power up the fancy runtime error iframe. For example, if you are using common chunks and an extra entry to create a vendor bundle with stuff like react, react-dom, react-router, etc. called
    vendor.js
    , and you've changed webpack's output to
    [name].js
    in development, you'd want to set this environment variable to
    /static/js/vendor.js
    . If you do not make this change, nothing bad will happen, you will simply not get the cool error overlay when there are runtime errors. You'll just see them in the console. Note: This does not impact production bundling.
  • process.env.VERBOSE
    : default is false, setting this to true will not clear the console when you make edits in development (useful for debugging).
  • process.env.PORT
    : The
    BUILD\_TARGET=server
    build listens on this port for all NODE_ENVs. default is
    3000
  • process.env.HOST
    : The IP address that the server will bind to. default is ```

0.0.0.0

, for INADDR\_ANY
- 

process.env.NODE_ENV

: 

'development'

 or 

'production'

- 

process.env.BUILD_TYPE

: 

'iso'

 for isomorphic/universal applications or 

'spa'

 for single page applications. The default is 

'iso'

. This is set by CLI arguments.
- 

process.env.BUILD_TARGET

: either 

'client'

 or 

'server'

- 

process.env.PUBLIC_PATH

: Only used in 

razzle build

. You can alter the 

webpack.config.output.publicPath

 of the client assets (bundle, css, and images). This is useful if you plan to serve your assets from a CDN. Make sure to _include_ a trailing slash (e.g. 

PUBLIC_PATH=https://cdn.example.com/

). If you are using React and altering the public path, make sure to also [include the 

crossorigin

 attribute](https://reactjs.org/docs/cdn-links.html#why-the-crossorigin-attribute) on your 
 tag in 

src/server.js

.
- 

process.env.CLIENT_PUBLIC_PATH

: The 

NODE_ENV=development

 build's 

BUILD_TARGET=client

 has a different 

PUBLIC_PATH

 than 

BUILD_TARGET=server

. Default is 

http://${process.env.HOST}:${process.env.PORT + 1}/


You can create your own custom environment variables that will be inlined during the build. They must start with

RAZZLE_

. Any other variables except the ones listed above will be ignored to avoid accidentally exposing a private key on the machine that could have the same name. Changing any environment variables will require you to restart the development server if it is running.

These environment variables will be defined for you on

process.env

. For example, having an environment variable named 

RAZZLE_SECRET_CODE

 will be exposed in your JS as 

process.env.RAZZLE_SECRET_CODE

.
### Runtime Variables

Using the dotenv package, or by defining variables in your shell (see below), you can get access to runtime environment variables. This is useful for services like Heroku which dynamically set

process.env.PORT

 for example. Be careful when referencing runtime variables in isomorphic code as they will be 

undefined

 in the browser, but defined when running in Node. This can lead to weird behavior. If you need to make runtime variables available to the browser, it is up to you to deliver them. You can stringify them and place them on 

window

...

// config.js export const runtimeConfig = typeof window !== 'undefined' ? { // client myThing: window.env.myThing, anotherThing: window.env.anotherThing, } : { // server myThing: process.env.MY_THING, anotherThing: process.env.ANOTHER_THING, };


Now we set

window.env

 as 

runtimeConfig

 when we go to render the HTML.

import App from './App'; import React from 'react'; import express from 'express'; import { renderToString } from 'react-dom/server'; import serialize from 'serialize-javascript'; // Safer stringify, prevents XSS attacks import { runtimeConfig } from './config'; const chunks = require(process.env.RAZZLE_CHUNKS_MANIFEST); const server = express(); server .disable('x-powered-by') .use(express.static(process.env.RAZZLE_PUBLIC_DIR)) .get('/*', (req, res) => { const markup = renderToString(); res.send( // prettier-ignore <meta http-equiv="X-UA-Compatible" content="IE=edge"><meta charset="utf-8"><title>Welcome to Razzle</title><meta name="viewport" content="width=device-width, initial-scale=1"> ${chunks.client.css.map(path =\>`)} ${markup}

${chunks.client.js.map(path =\> ``)} ` ); }); export default server;

### Adding Temporary Environment Variables In Your Shell

Defining environment variables can vary between OSes. It’s also important to know that this manner is temporary for the life of the shell session.

#### Windows (cmd.exe)

set RAZZLE_SECRET_CODE=abcdef&&npm start


(Note: the lack of whitespace is intentional.)

#### Linux, macOS (Bash)

RAZZLE_SECRET_CODE=abcdef npm start


### Adding Environment Variables In 

.env


To define permanent environment variables, create a file called .env in the root of your project:

RAZZLE_SECRET_CODE=abcdef


### Expanding Environment Variables In 

.env


Expand variables already on your machine for use in your

.env

 file.

For example, to get the environment variable

npm_package_version

:

RAZZLE_VERSION=$npm_package_version # also works: # RAZZLE_VERSION=${npm_package_version}


Or expand variables local to the current

.env

 file:

DOMAIN=www.example.com RAZZLE_FOO=$DOMAIN/foo RAZZLE_BAR=$DOMAIN/bar


#### What other 

.env

 files are can be used?

- 

.env

: Default.
- 

.env.local

: Local overrides. **This file is loaded for all environments except test.**
- 

.env.development

, 

.env.test

, 

.env.production

: Environment-specific settings.
- 

.env.development.local

, 

.env.test.local

, 

.env.production.local

: Local overrides of environment-specific settings.

Files on the left have more priority than files on the right:

- 

npm start

: 

.env.development.local

, 

.env.development

, 

.env.local

, 

.env

- 

npm run build

: 

.env.production.local

, 

.env.production

, 

.env.local

, 

.env

- 

npm test

: 

.env.test.local

, 

.env.test

, 

.env

 (note 

.env.local

 is missing)

These variables will act as the defaults if the machine does not explicitly set them.  
Please refer to the [dotenv documentation](https://github.com/motdotla/dotenv) for more details.

> Note: If you are defining environment variables for development, your CI and/or hosting platform will most likely need these defined as well. Consult their documentation how to do this. For example, see the documentation for [Travis CI](https://docs.travis-ci.com/user/environment-variables/) or [Heroku](https://devcenter.heroku.com/articles/config-vars).

## How Razzle works (the secret sauce)

**TL;DR**: 2 configs, 2 ports, 2 webpack instances, both watching and hot reloading the same filesystem, in parallel during development and a little

webpack.output.publicPath

 magic.

In development mode (

razzle start

), Razzle bundles both your client and server code using two different webpack instances running with Hot Module Replacement in parallel. While your server is bundled and run on whatever port you specify in 

src/index.js

 (

3000

 is the default), the client bundle (i.e. entry point at 

src/client.js

) is served via 

webpack-dev-server

 on a different port (

3001

 by default) with its 

publicPath

 explicitly set to 

localhost:3001

 (and not 

/

 like many other setups do). Then the server's html template just points to the absolute url of the client JS: 

localhost:3001/static/js/client.js

``` . Since both webpack instances watch the same files, whenever you make edits, they hot reload at exactly the same time. Best of all, because they use the same code, the same webpack loaders, and the same babel transformations, you never run into a React checksum mismatch error.

Inspiration

Author


MIT License

Contributors

Thanks goes to these wonderful people (emoji key):

|
Jared Palmer

πŸ’¬ πŸ’» 🎨 πŸ“– πŸ’‘ πŸ€” πŸ‘€ ⚠️ πŸ”§ |
Jari Zwarts

πŸ’¬ πŸ’» πŸ€” πŸ”Œ πŸ‘€ |
Dan Abramov

πŸ’» πŸ€” |
Eric Clemmons

πŸ’» πŸ€” |
Zino Hofmann

πŸ’‘ |
Lucas Terra

πŸ’» πŸ’‘ πŸ”Œ |
Ray Andrew

πŸ’» πŸ’‘ πŸ”Œ | | :---: | :---: | :---: | :---: | :---: | :---: | :---: | |
Erik Engi

πŸ“– πŸ“ πŸ’‘ πŸ› |

This project follows the all-contributors specification. Contributions of any kind welcome!

We use cookies. If you continue to browse the site, you agree to the use of cookies. For more information on our use of cookies please see our Privacy Policy.