JavaScript by Example by S Dani Akash

Author:S, Dani Akash [S, Dani Akash]
Language: eng
Format: azw3
Tags: COM060160 - COMPUTERS / Web / Web Programming, COM051260 - COMPUTERS / Programming Languages / JavaScript, COM060080 - COMPUTERS / Web / General
Publisher: Packt Publishing
Published: 2017-08-30T04:00:00+00:00

Shipping the code

Now that you have learned how to generate production builds, what if you want to send this code to someone else? Say the DevOps team or the server administrator. In this case, if you are using version control, add the dist/ directory, the node_modules/ directory, and the .env files to your ignore list. Send the code without these two directories and the .env file. The other person should be able to figure out which environment variables to use using the .env.example file, creating the .env file, and also using the npm install and npm run webpack commands to generate the node_modules/ and dist/ directories.

For all the other steps, neatly document the procedure in a README.md file in your project root folder and send it along with the other files.

The main reason why sharing the .env file should be avoided is because the environment variables might contain sensitive information and should not be transported or stored in version control as plain text.

You have now learned about generating production builds for your applications built with Webpack. Now, the Meme Creator app does not have a production build yet! I'll let you use the webpack.config.js file used in this chapter as a reference. So, go ahead and create a production build for your Meme Creator.

Download

Copyright Disclaimer:
This site does not store any files on its server. We only index and link to content provided by other sites. Please contact the content providers to delete copyright contents if any and email us, we'll remove relevant links or contents immediately.