neutrino-preset-react is a Neutrino preset that supports building React web applications.
neutrino-preset-react can be installed via the Yarn or npm clients. Inside your project, make sure
neutrino-preset-react are development dependencies. You will also need React and React DOM for actual
❯ yarn add --dev neutrino neutrino-preset-react❯ yarn add react react-dom
❯ npm install --save-dev neutrino neutrino-preset-react❯ npm install --save react react-dom
neutrino-preset-react follows the standard project layout specified by Neutrino. This
means that by default all project source code should live in a directory named
src in the root of the
to import your compiled project.
After installing Neutrino and the React preset, add a new directory named
src in the root of the project, with
a single JS file named
index.js in it.
❯ mkdir src && touch src/index.js
This React preset exposes an element in the page with an ID of
root to which you can mount your application. Edit
src/index.js file with the following:
import React from 'react';import render from 'react-dom';;
Now edit your project's package.json to add commands for starting and building the application:
If you are using
.neutrinorc.js, add this preset to your use array instead of
moduleexports =use: 'neutrino-preset-react';
Start the app, then open a browser to the address in the console:
❯ yarn start✔ Development server running on: http://localhost:5000✔ Build completed
❯ npm start✔ Development server running on: http://localhost:5000✔ Build completed
neutrino-preset-react builds static assets to the
build directory by default when running
neutrino build. Using
the quick start example above as a reference:
❯ yarn build✔ Building project completedHash: b26ff013b5a2d5f7b824Version: webpack 2.6.1Time: 9773msAsset Size Chunks Chunk Namesindex.dfbad882ab3d86bfd747.js 181 kB index [emitted] indexpolyfill.57dabda41992eba7552f.js 69.2 kB polyfill [emitted] polyfillruntime.3d9f9d2453f192a2b10f.js 1.51 kB runtime [emitted] runtimeindex.html 846 bytes [emitted]✨ Done in 14.62s.
You can either serve or deploy the contents of this
build directory as a static site.
If you wish to copy files to the build directory that are not imported from application code, you can place
them in a directory within
static. All files in this directory will be copied from
neutrino-preset-web preset loads assets relative to the path of your application by setting Webpack's
./. If you wish to load
assets instead from a CDN, or if you wish to change to an absolute path for your application, customize your build to
output.publicPath. See the Customizing section below.
You can provide custom options and have them merged with this preset's default options to easily affect how this
preset builds. You can modify React preset settings from
.neutrinorc.js by overriding with an options object. Use
an array pair instead of a string to supply these options in
The following shows how you can pass an options object to the React preset and override its options. See the Web documentation for specific options you can override with this object.
moduleexports =use:'neutrino-preset-react'/* preset options */// Example: disable Hot Module Replacementhot: false// Example: change the page titlehtml:title: 'Epic React App'// Add additional Babel plugins, presets, or env optionsbabel:// Override options for babel-preset-envpresets:'babel-preset-env'// Passing in targets to babel-preset-env will replace them// instead of merging themtargets:browsers:'last 1 Chrome versions''last 1 Firefox versions';
To override the build configuration, start with the documentation on customization.
neutrino-preset-react does not use any additional named rules, loaders, or plugins that aren't already in use by the
Web preset. See the Web documentation customization
for preset-specific configuration to override.
By following the customization guide and knowing the rule, loader, and plugin IDs from
neutrino-preset-web, you can override and augment the build by providing a function to your
array. You can also make these changes from the Neutrino API in custom middleware.
By defining an entry point named
vendor you can split out external dependencies into a chunk separate
from your application code.
Example: Put React and React DOM into a separate "vendor" chunk:
neutrino-preset-react supports Hot Module Replacement your app using React Hot Loader, it does require some
application-specific changes in order to operate.
react-hot-loader as a dependency, this must be React Hot Loader v3+ (currently in beta):
❯ yarn add react-hot-loader@next
❯ npm install --save react-hot-loader@next
indexentry point (defaults to
neutrino.options.entry), import an
react-hot-loader. The main file may be named
index.jsx. The extension is resolved by Webpack.
hotacceptance to call this function.
import React from 'react';import render from 'react-dom';import AppContainer from 'react-hot-loader';import MyApp from './MyApp';const load =;if modulehotmodulehot;;