Book Image

JavaScript by Example

By : Dani Akash S
Book Image

JavaScript by Example

By: Dani Akash S

Overview of this book

JavaScript is the programming language that all web developers need to learn. The first item on our JavaScript to-do list is building g a To-do list app, which you'll have done by the end of the first chapter. You'll explore DOM manipulation with JavaScript and work with event listeners. You'll work with images and text to build a Meme creator. You will also learn about ES (ECMAScript) classes, and will be introduced to layouts using the CSS3 Flexbox. You'll also develop a responsive Event Registration form that allows users to register for your upcoming event and use charts and graphics to display registration data. You will then build a weather application, which will show you different ways perform AJAX requests and work with dynamic, external data. WebRTC enables real-time communication in a web browser; you'll learn how to use it when you build a real-time video-call and chat application later in the book. Towards the end of the book, you will meet React, Facebook's JavaScript library for building user interfaces. You'll throw together a blog with React, and get a feel for why this kind of JavaScript framework is used to build large-scale applications. To make your blog more maintainable and scalable, you'll use Redux to manage data across React components.
Table of Contents (8 chapters)

Generating a production build

You might have noticed something about both the Meme Creator and the Event Registration apps. The apps load plain HTML first; after that, styles are loaded. This makes the applications look plain for a moment. This problem does not exist in the ToDo List app because we load CSS first in the ToDo List app. In the Meme Creator app, there was an optional section called Optimizing Webpack builds for different environments. This might be a good time to read it. If you haven't read it yet, go back, give that section a read, and come back to generate the production build.

So far, our app has been working in a development environment. Remember? In the .env file, I told you to set NODE_ENV=dev. This is because, when you set NODE_ENV=production as per the webpack.config.js file I created, Webpack will go into production mode. The npm run watch command...