{"componentChunkName":"component---src-templates-lesson-js","path":"/phoenix-chat/basics-of-webpack","result":{"data":{"mdx":{"body":"function _extends() { _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; }; return _extends.apply(this, arguments); }\n\nfunction _objectWithoutProperties(source, excluded) { if (source == null) return {}; var target = _objectWithoutPropertiesLoose(source, excluded); var key, i; if (Object.getOwnPropertySymbols) { var sourceSymbolKeys = Object.getOwnPropertySymbols(source); for (i = 0; i < sourceSymbolKeys.length; i++) { key = sourceSymbolKeys[i]; if (excluded.indexOf(key) >= 0) continue; if (!Object.prototype.propertyIsEnumerable.call(source, key)) continue; target[key] = source[key]; } } return target; }\n\nfunction _objectWithoutPropertiesLoose(source, excluded) { if (source == null) return {}; var target = {}; var sourceKeys = Object.keys(source); var key, i; for (i = 0; i < sourceKeys.length; i++) { key = sourceKeys[i]; if (excluded.indexOf(key) >= 0) continue; target[key] = source[key]; } return target; }\n\n/* @jsx mdx */\nvar _frontmatter = {\n  \"title\": \"Basics of Webpack\",\n  \"order\": 4,\n  \"free\": true,\n  \"active\": true,\n  \"tech\": [\"react\", \"webpack\"]\n};\n\nvar makeShortcode = function makeShortcode(name) {\n  return function MDXDefaultShortcode(props) {\n    console.warn(\"Component \" + name + \" was not imported, exported, or provided by MDXProvider as global scope\");\n    return mdx(\"div\", props);\n  };\n};\n\nvar layoutProps = {\n  _frontmatter: _frontmatter\n};\nvar MDXLayout = \"wrapper\";\nreturn function MDXContent(_ref) {\n  var components = _ref.components,\n      props = _objectWithoutProperties(_ref, [\"components\"]);\n\n  return mdx(MDXLayout, _extends({}, layoutProps, props, {\n    components: components,\n    mdxType: \"MDXLayout\"\n  }), mdx(\"h1\", null, \"Basics of Webpack\"), mdx(\"ul\", null, mdx(\"li\", {\n    \"parentName\": \"ul\"\n  }, \"Set up Webpack\"), mdx(\"li\", {\n    \"parentName\": \"ul\"\n  }, \"Hello World!\")), mdx(\"p\", null, \"In this section, we set up Webpack and get our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"Hello World!\"), \" app running.\"), mdx(\"h2\", null, \"Webpack configuration\"), mdx(\"p\", null, \"Now that we have all of our NPM dependencies set up, we need to configure Webpack. As mentioned before, this is not the simplest task. There are a seemingly limitless number of configuration options, but for now, we will only use the minimum.\"), mdx(\"p\", null, \"Create a file using the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"touch\"), \" command in your \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"/phoenix-chat-frontend\"), \" directory called \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack.config.js\"), \".\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ touch webpack.config.js\\n\")), mdx(\"p\", null, \"In that file, add the following configuration options, which we will go over line-by-line below the code:\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-js\",\n    \"parentName\": \"pre\"\n  }, \"var path = require(\\\"path\\\")\\nvar webpack = require(\\\"webpack\\\")\\n\\nmodule.exports = {\\n  devtool: \\\"eval\\\",\\n  entry: [\\\"webpack-dev-server/client?http://localhost:3000\\\", \\\"./app/index\\\"],\\n  output: {\\n    path: path.join(__dirname, \\\"dist\\\"),\\n    filename: \\\"bundle.js\\\",\\n  },\\n  module: {\\n    loaders: [\\n      {\\n        test: /\\\\.js$/,\\n        loaders: [\\\"babel\\\"],\\n        exclude: /node_modules/,\\n        include: path.join(__dirname, \\\"app\\\"),\\n      },\\n    ],\\n  },\\n  resolve: {\\n    extensions: [\\\"\\\", \\\".js\\\"],\\n  },\\n}\\n\")), mdx(\"p\", null, \"The first line requires the Node's \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"path\"), \", which is used to keep track of directory names. This is not strictly necessary, but makes directory paths clearer.\"), mdx(\"p\", null, \"The second line requires \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack\"), \". We need this because we are going to use some of the plugins from Webpack later on in the configuration.\"), mdx(\"p\", null, \"Next we have our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"devtool\"), \", which we set to \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"eval\"), \". This just sets your debugging tool to one of \", mdx(\"a\", {\n    \"href\": \"https://webpack.github.io/docs/configuration.html#devtool\",\n    \"parentName\": \"p\"\n  }, \"several options\"), \", but almost everyone uses \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"eval\"), \" because it builds faster. If you want better bug tracking, you should use \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"source-map\"), \" or \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"inline-source-map\"), \".\"), mdx(\"p\", null, \"The next configuration option is \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"entry\"), \". Entry is an important concept in Webpack because it defines all the modules that are to be loaded when you start the app, with the last one being exported. This is an important piece to understand, so we will go into greater detail.\"), mdx(\"p\", null, \"The first entry point is the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack-dev-server\"), \", which we want to run our app through first. Next, we run it through the Webpack hot loader, which hot-loads our code and allows the changes you make to take effect immediately without losing the state of your app. The last thing is \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app/index\"), \". This will finally export whatever we eventually put in the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.js\"), \" file, which we will create shortly.\"), mdx(\"p\", null, \"You might be wondering at this point why we left off the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".js\"), \" part of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.js\"), \" in our configuration file. That's because of the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"resolve\"), \" configuration option, which allows us to leave off the file extensions of any named file type--in this case, \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".js\"), \".\"), mdx(\"p\", null, \"The next configuration option is \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"output\"), \". This is another important part of webpack to be aware of. Because React is all JavaScript, Webpack is able to bundle everything into a single file (though not necessarily one file, as we will see much later in this course) and insert it into a script tag in your app.\"), mdx(\"p\", null, mdx(\"img\", {\n    \"src\": \"/learnphoenix-static-assets/images/webpack_bundle.png\",\n    \"alt\": \"webpack bundle\",\n    \"parentName\": \"p\"\n  })), mdx(\"p\", null, \"In our case, we are cleverly naming our bundle, \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"bundle.js\"), \". We are also specifying the location of all static assets to be compiled into \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"dist/\"), \". If you want to see webpack in action or look at what would be built in production, you can run \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack\"), \" from the command line and it will compile your app and drop it in \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"phoenix-chat-frontend/dist\"), \".\"), mdx(\"p\", null, \"The next line is our list of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"loaders\"), \". By the time this project is through, we will have several additional loaders for different types of files. This is where you tell Webpack how to handle different file types. You can handle images (\", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".png\"), \", etc), styling (\", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".less\"), \", \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".scss\"), \", etc), and just about any other type of file imaginable--even file extensions that you set arbitrarily, such as \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".potato\"), \". Loaders are among the most useful features of webpack, and they are the easiest to understand.\"), mdx(\"p\", null, \"Also within our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"loaders\"), \", we are telling it to ignore any files within our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"node_modules\"), \" directory, because those files are already compiled, and we telling it to explicitly look for files within our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app\"), \" directory.\"), mdx(\"p\", null, \"The flow chart below shows the logic of this basic webpack app.\"), mdx(\"img\", {\n    src: \"https://imgs.xkcd.com/comics/flow_charts.png\"\n  }), mdx(\"p\", null, \"We now have a functional (if basic) webpack configuration.\"), mdx(\"h2\", null, \"Server configuration\"), mdx(\"p\", null, \"The last piece of configuration we need is to configure our server. Recall we changed our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"npm start\"), \" script to call a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"server.js\"), \" file so we could add some additional configuration. So the first thing we need to do is create the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"server.js\"), \" file in our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"/phoenix-chat-frontend\"), \" directory.\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ touch server.js\\n\")), mdx(\"p\", null, \"In that file, add the following configuration:\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-js\",\n    \"parentName\": \"pre\"\n  }, \"var webpack = require(\\\"webpack\\\")\\nvar WebpackDevServer = require(\\\"webpack-dev-server\\\")\\nvar config = require(\\\"./webpack.config\\\")\\n\\nnew WebpackDevServer(webpack(config), {\\n  historyApiFallback: true,\\n}).listen(3000, \\\"localhost\\\", function (err, res) {\\n  err ? console.log(err) : console.log(\\\"Listening at localhost:3000\\\")\\n})\\n\")), mdx(\"p\", null, \"First we declare our dependencies for this module (\", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack\"), \", \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack-dev-server\"), \", and \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"webpack.config\"), \"), then we create a new \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"WebpackDevServer\"), \", with some of the options from our Webpack configuration and tell it to listen on \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"port 3000\"), \".\"), mdx(\"p\", null, \"The \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"historyApiFallback\"), \" is necessary for handling route changes. We will start out with something called \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"hashHistory\"), \" (explained in detail later), which handles all routing on the client with no server-side configuration necessary. This flag makes routing possible for single page apps. If you want to dig deeper into why this is, check out \", mdx(\"a\", {\n    \"href\": \"https://github.com/bripkens/connect-history-api-fallback\",\n    \"parentName\": \"p\"\n  }, \"this resource\"), \".\"), mdx(\"p\", null, \"If there is an error, it tells us there was an error. Otherwise, it logs \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"Listening at localhost:3000\"), \".\"), mdx(\"h2\", null, \"HTML, React, and ReactDOM\"), mdx(\"p\", null, \"There are only two remaining additions we need to make to get our \\\"Hello World!\\\" app running. First we need an \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.html\"), \" in our root directory, then we need to create our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app/index.js\"), \" file to render to the page.\"), mdx(\"p\", null, \"Go ahead and create an \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.html\"), \" file in the root directory and add the following.\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ touch index.html\\n\")), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-html\",\n    \"parentName\": \"pre\"\n  }, \"<html>\\n  <head>\\n    <title>PhoenixChat.io</title>\\n    <meta\\n      name=\\\"description\\\"\\n      content=\\\"Free, easy-to-use React component for real-time chat with prospective customers.\\\"\\n    />\\n    <meta name=\\\"viewport\\\" content=\\\"width=device-width, initial-scale=1\\\" />\\n    <meta charset=\\\"UTF-8\\\" />\\n  </head>\\n  <body>\\n    <div id=\\\"root\\\"></div>\\n    <script src=\\\"bundle.js\\\"></script>\\n  </body>\\n</html>\\n\")), mdx(\"p\", null, \"Google actually doesn't care about \", mdx(\"a\", {\n    \"href\": \"https://support.google.com/webmasters/answer/79812?hl=en\",\n    \"parentName\": \"p\"\n  }, \"most meta tags\"), \", but it does care about the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"description\"), \" tag.\"), mdx(\"p\", null, \"The next \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"meta\"), \" tag is the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"viewport\"), \" tag, which makes it possible to resize your app based on the size of the screen that is viewing it--namely, this is what makes viewing your site on a mobile device possible. Pretty much every app should have this tag.\"), mdx(\"p\", null, \"We are also including a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"meta\"), \" tag that sets the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"charset\"), \" to \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"UTF-8\"), \". This is not usually necessary since most browsers will assume this is the case. This allows you to use lots of new characters and symbols. For more on this, check out \", mdx(\"a\", {\n    \"href\": \"https://en.wikipedia.org/wiki/UTF-8\",\n    \"parentName\": \"p\"\n  }, \"UTF-8\"), \".\"), mdx(\"p\", null, \"Next is the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"body\"), \", in which we are creating a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"div\"), \" with an \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"id\"), \" of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"root\"), \". It is within this \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"div\"), \" that we will create our entire app. Though it is possible to render your app directly to \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"document.body\"), \", it is bad practice and should be avoided. If this point is confusing, it will become clear once we fill out our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.js\"), \" file.\"), mdx(\"p\", null, \"The last thing we add is a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"script\"), \" tag that links to \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"bundle.js\"), \". This is where Webpack puts all of our React code to allow us to render our app. You may recall in our Webpack configuration we set our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"output\"), \" to have a filename of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"bundle.js\"), \" and a path of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"dist\"), \". This is where we reference that configuration option.\"), mdx(\"p\", null, \"Let's create a few basic files that we'll use later while building the app. First, create an \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app\"), \" directory within \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"/phoenix-chat-frontend\"), \", and then a file called \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.js\"), \" within app:\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ mkdir app\\n$ touch app/index.js\\n\")), mdx(\"p\", null, \"Now, within our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app/index.js\"), \" file, we want to write the code that will render our app. First, let's create a React component that will render the text \\\"Hello World!\\\" within a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"div\"), \".\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-jsx\",\n    \"parentName\": \"pre\"\n  }, \"import React from \\\"react\\\"\\n\\nclass HelloWorld extends React.Component {\\n  render() {\\n    return <div>Hello World!</div>\\n  }\\n}\\n\")), mdx(\"p\", null, \"The next thing we need to do is render that component to the DOM. For that, we need \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"react-dom\"), \". Change your code to the following to tell ReactDOM to render your component under the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"div\"), \" we created in our \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"index.html\"), \" file with an \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"id\"), \" of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"root\"), \".\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-jsx\",\n    \"parentName\": \"pre\"\n  }, \"import React from \\\"react\\\"\\nimport ReactDOM from \\\"react-dom\\\"\\n\\nclass HelloWorld extends React.Component {\\n  render() {\\n    return <div>Hello World!</div>\\n  }\\n}\\n\\nReactDOM.render(<HelloWorld />, document.getElementById(\\\"root\\\"))\\n\")), mdx(\"h2\", null, \"Hello World!\"), mdx(\"p\", null, \"We're finally done with configuration! Now it's time to start the app. Within the \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"phoenix-chat-frontend/\"), \" directory, run the following commands to install all your \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"npm\"), \" dependencies and start your app (using the script we created at the beginning of this lesson):\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ npm install && npm start\\n\")), mdx(\"p\", null, \"You should now have an app that renders \\\"Hello World!\\\" to the screen like this\"), mdx(\"p\", null, mdx(\"em\", {\n    \"parentName\": \"p\"\n  }, \"coming soon\")), mdx(\"h2\", null, \"Additional\"), mdx(\"p\", null, \"There are a few optional configurations you can do that will save you some headache down the road. If you're using git for version tracking, you should probably add a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".gitignore\"), \" to make sure you don't commit your \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"node_modules\"), \". Within a \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".gitignore\"), \" file in the root of your app, simply add the line \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"node_modules\"), \" and git will not track anything in that folder.\"), mdx(\"p\", null, \"If you're on a Mac, you should probably add \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \".DS_Store\"), \" to this list as well, because they're annoying. And while you're at it, add \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"npm-debug.log\"), \" incase you try to run \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"npm start\"), \" from the wrong directory, or cause any other errors with npm. And since everything in \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"dist\"), \" will be created from the contents of \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"app\"), \", we can safely ignore its contents.\"), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-bash\",\n    \"parentName\": \"pre\"\n  }, \"$ touch .gitignore\\n\")), mdx(\"pre\", null, mdx(\"code\", {\n    \"className\": \"language-text\",\n    \"parentName\": \"pre\"\n  }, \"node_modules\\n.DS_Store\\nnpm-debug.log\\ndist\\n\")), mdx(\"p\", null, \"A few additional notes regarding common practices. JavaScript generally uses \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"camelCase\"), \", Elixir uses \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"PascalCase\"), \", and erlang uses \", mdx(\"inlineCode\", {\n    \"parentName\": \"p\"\n  }, \"under_scores\"), \". You will occasionally use erlang code within Phoenix.\"));\n}\n;\nMDXContent.isMDXComponent = true;","excerpt":"Basics of Webpack Set up Webpack Hello World! In this section, we set up Webpack and get our  Hello World!  app running. Webpack…","frontmatter":{"title":"Basics of Webpack","order":4,"active":true,"free":true,"tech":["react","webpack"]}}},"pageContext":{"slug":"basics-of-webpack","prevNode":{"frontmatter":{"title":"Basics of React","active":true,"free":true,"order":3,"tech":["react","webpack","babel"]},"fields":{"slug":"basics-of-react"}},"nextNode":{"frontmatter":{"title":"Routes and Views","active":true,"free":true,"order":5,"tech":["react","react-router"]},"fields":{"slug":"routes-and-views"}}}},"staticQueryHashes":["1723017916"]}