Questions And Answers

More Tutorials

React setup a basic webpack, react and babel environment

Step 1: Install Node.js

The build pipeline you will be building is based in Node.js so you must ensure in the first instance that you have this installed. For instructions on how to install Node.js you can checkout the SO docs for that here

Step 2: Initialise your project as an node module

Open your project folder on the command line and use the following command:

npm init

For the purposes of this example you can feel free to take the defaults or if you'd like more info on what all this means you can check out this SO doc on setting up package configuration.

Step 3: Install necessary npm packages

Run the following command on the command line to install the packages necessary for this example:

npm install --save react react-dom

Then for the dev dependencies run this command:

npm install --save-dev babel-core babel-preset-react babel-preset-es2015 webpack babel-loader cssloader style-loader file-loader image-webpack-loader

Finally webpack and webpack-dev-server are things that are worth installing globally rather than as a dependency

of your project, if you'd prefer to add it as a dependency then that will work to, I don't. Here is the command to run:

npm install --global webpack webpack-dev-server

Step 3: Add a .babelrc file to the root of your project

This will setup babel to use the presets you've just installed. Your .babelrc file should look like this:

 "presets": ["react", "es2015"]

Step 4: Setup project directory structure

Set yourself up a directory stucture that looks like the below in the root of your directory:
|- node_modules
|- src/
|- components/
|- images/
|- styles/
|- index.html
|- index.jsx
|- .babelrc
|- package.json

NOTE: The node_modules, .babelrc and package.json should all have already been there from previous steps I just included them so you can see where they fit.

Step 5: Populate the project with the Hello World project files

This isn't really important to the process of building a pipeline so I'll just give you the code for these and you can copy paste them in:

import React, { Component } from 'react';
class HelloWorldComponent extends Component {
 constructor(props) {
 this.state = {name: 'Student'};
 this.handleChange = this.handleChange.bind(this);
 handleChange(e) {
 render() {
 return (
 <div className="image-container">
 <img src="./images/myImage.gif" />
 <div className="form">
 <input type="text" onChange={this.handleChange} />
 My name is {} and I'm a clever cloggs because I built a React build
export default HelloWorldComponent;


Feel free to substitute this with any image you'd like it's simply there to prove the point that we can bundle up images as well. If you provide your own image and you name it something different then you'll have to update the HelloWorldComponent.jsx to reflect your changes. Equally if you choose an image with a different file extension then you need to modify the test property of the image loader in the webpack.config.js with appropriate regex to match your new file extension..


.form {
 margin: 25px;
 padding: 25px;
 border: 1px solid #ddd;
 background-color: #eaeaea;
 border-radius: 10px;
.form div {
 padding-top: 25px;
.image-container {
 display: flex;
 justify-content: center;
<!DOCTYPE html>
<html lang="en">
 <meta charset="UTF-8">
 <title>Learning to build a react pipeline</title>
 <div id="content"></div>
 <script src="app.js"></script>
import React from 'react';
import { render } from 'react-dom';
import HelloWorldComponent from './components/HelloWorldComponent.jsx';
render(<HelloWorldComponent />, document.getElementById('content'));
Step 6: Create webpack configuration
Create a file called webpack.config.js in the root of your project and copy this code into it:
var path = require('path');
var config = {
 context: path.resolve(__dirname + '/src'),
 entry: './index.jsx',
 output: {
 filename: 'app.js',
 path: path.resolve(__dirname + '/dist'),
 devServer: {
 contentBase: path.join(__dirname + '/dist'),
 port: 3000,
 open: true,
 module: {
 loaders: [
 test: /\.(js|jsx)$/,
 exclude: /node_modules/,
 loader: 'babel-loader'
 test: /\.css$/,
 loader: "style!css"
 test: /\.gif$/,
 loaders: [
 { test: /\.(html)$/,
 loader: "file?name=[path][name].[ext]"
module.exports = config;

Step 7: Create npm tasks for your pipeline

To do this you will need to add two properties to the scripts key of the JSON defined in the package.json file in the root of your project. Make your scripts key look like this:

"scripts": {
 "start": "webpack-dev-server",
 "build": "webpack",
 "test": "echo \"Error: no test specified\" && exit 1"

The test script will have already been there and you can choose whether to keep it or not, it's not important to this example.

Step 8: Use the pipeline

From the command line, if you are in the project root directory you should now be able to run the command:

npm run build

This will bundle up the little application you've built and place it in the dist/ directory that it will create in the root of your project folder.

If you run the command:

npm start

Then the application you've built will be served up in your default web browser inside of a webpack dev server instance.


In this page (written and validated by ) you learned about React setup a basic webpack react and babel environment . What's Next? If you are interested in completing React tutorial, your next topic will be learning about: React createClass vs extends Component.

Incorrect info or code snippet? We take very seriously the accuracy of the information provided on our website. We also make sure to test all snippets and examples provided for each section. If you find any incorrect information, please send us an email about the issue:

Share On:

Mockstacks was launched to help beginners learn programming languages; the site is optimized with no Ads as, Ads might slow down the performance. We also don't track any personal information; we also don't collect any kind of data unless the user provided us a corrected information. Almost all examples have been tested. Tutorials, references, and examples are constantly reviewed to avoid errors, but we cannot warrant full correctness of all content. By using, you agree to have read and accepted our terms of use, cookies and privacy policy.