There are a few different common patterns that are used to set up the structure of your modules in Node.js. We'll be discussing 5 such common patterns. One of the main things to know/remember, which will help you immensely as you're trying to understand these different patterns, is
If you recall from the Intro to Node post, one of the main requirements of having JavaScript be able to work on a server is to have code that can be more easily organized. Thus far in JavaScript, we're used to having each JavaScript file be completely on its own,
Express is a "fast, unopinionated, minimalist web framework for Node.js." It is considered a very thin, lightweight framework that uses Node.js APIs to take common uses of Node.js and abstract (simplify) them for easier use by the developer. In this document, we will run through how to
In just about any useful application you'll make, you'll need a way to persist (keep) data. Otherwise, every time you refresh the page, close the browser, etc. you will lose everything you put into the application. Which obviously makes for a pretty terrible application... There are a number of options
So here it is. The big sha-bang. You are going to build a full-stack final project. You will pick your own theme. Here is how you should spend your time (Due to the fact that your first job will most likely be front-end work): * 50% Angular * 30% HTML/CSS/Bootstrap/