Gain insights into Node.js fundamentals, event loops, and multithreading. Delve into file systems, global objects, and advanced modules. Discover how to create a food delivery web application.

final.tar.gz

TCP_job

HTTP_test

Project_3

Project_1

Project_2

Project_0

timer_demo

UDP_job

Project_demo

sayMyName

logger

nodemon app

npm terminal

UDP_chat_nodemon

TCP_chat_nodemon

run-app.js

terminal-app.js

Node.js is an open-source, cross-platform, JavaScript runtime environment that executes JavaScript code outside of a web browser. This course is your guide for learning the fundamentals of Node.js.

In this course, you'll start by understanding the inner workings of Node.js. More specifically, you’ll explore its features, how event loops work, and how multithreading works. You’ll then move on to the fundamentals of Node.js like file systems, global objects, and the Buffer class.

In the latter half of the course, you’ll explore more advanced concepts like modules,  events,  and packages. At the end of this course, you will get hands-on with Node.js and create your own food delivery web application.

By the end of this course, you will have a new, in-demand skill to put on your resume and a cool project to add to your portfolio.

Learn Node.js: The Complete Course for Beginners

# Packages in Node.js
Node.js packages allow us to reuse code that has already been written by other people. This concept is not something that is unique to Node.js; Python and its package installer, pip, accomplish what Node.js does with npm. So what exactly is a package?
 

Here are some famous packages:
- [React](https://reactjs.org/) is a JavaScript library that allows us to create interactive user interfaces.
- [Express](https://expressjs.com/) is a minimal Node.js web application framework that provides a robust set of features for web and mobile applications.
- [Axios](https://github.com/axios/axios) is a promise-based HTTP client for the browser and Node.js. 


A package must contain a `package.json` file in order to be published to the npm registry. Since modules are not required to have a `package.json` file, not all modules are packages. Only modules that have a `package.json` file are packages.

# npm
**npm** is the package manager for Node.js; it is a software registry that makes sharing and accessing packages easy. npm is installed when Node.js is installed. Each project has dependencies that are listed in its package.json. The dependencies can be installed using a single line. The [website](https://www.npmjs.com/) makes searching for packages very easy. Packages can then be installed from the npm #key# CLI: Command Line Interface #key#. Try installing React in the terminal below. Use the command `npm install react`.




# Why do we use packages?
There are quite a few benefits of using packages. Let's take a look at a few.

### Don't reinvent the wheel
The saying, *"If it's not broken, don't fix it,"* can most certainly be applied to code. Some of the packages hosted on npm may have most of the functionality that you might be looking to implement in your own code. The Node.js `http` module can be used to create a simple server. However, adding additional functionality can result in a lot of repeated and, often, complicated code. [Express](https://expressjs.com/) can simplify this process and can get your work done in a fraction of the time and much less code.

### Tried and tested
While it is relatively easy to submit your own package to npm, some of the packages hosted there have been around for quite some time. This allows the community to build and improve packages -- often adding more features, making them more efficient, or keeping them up to date with the newest version of Node.js. Most packages provide a sense of reliability that only comes from years of continuous improvement.

Introduction

Fundamentals

Advanced Topics

Packages

Project

Appendix

What Are Packages?

Packages in Node.js

npm

Why do we use packages?

Don’t reinvent the wheel

Tried and tested