Skip to main content
Explore
Log in
Get started
Someone wanted to learn this too, so Grasp built them a personal learning path.
Create your own
Running a Node.js Backend
Module 1
Prepare the Windows Backend Environment
1
Obtaining Backend Files Before Running Setup Commands
Explain why the backend project files must be obtained before running its setup commands.
Explain why the backend project files must be obtained before running its setup commands.
2
Verify Node.js and npm Versions in PowerShell
Verify that Node.js and npm are available from PowerShell using version commands.
Verify that Node.js and npm are available from PowerShell using version commands.
3
Installing the Current Node.js LTS Release
Install a current Node.js LTS release when Node.js or npm is unavailable.
Install a current Node.js LTS release when Node.js or npm is unavailable.
4
Locating the Project Folder with the Backend Package.json
Locate the project folder that contains the backend directory and its package.json file.
Locate the project folder that contains the backend directory and its package.json file.
5
Navigate to the Backend Directory in PowerShell
Navigate to the backend directory in PowerShell and confirm the current location.
Navigate to the backend directory in PowerShell and confirm the current location.
Module 2
Install and Run the Backend
6
Installing Dependencies and Distinguishing Warnings from Failures
Install the dependencies declared in package.json with npm install and distinguish warnings from installation failures.
Install the dependencies declared in package.json with npm install and distinguish warnings from installation failures.
7
Using the package.json Dev Script with npm run dev
Identify the purpose of the dev script in package.json and start it with npm run dev.
Identify the purpose of the dev script in package.json and start it with npm run dev.
8
Restarting the Backend Development Process
Identify the backend's successful startup message and local address, then stop and restart the development process.
Identify the backend's successful startup message and local address, then stop and restart the development process.
9
Diagnosing Missing package.json Errors in the Wrong Directory
Diagnose a missing package.json error caused by running npm commands from the wrong directory.
Diagnose a missing package.json error caused by running npm commands from the wrong directory.
10
Troubleshooting Node.js, npm, and bcryptjs Errors
Diagnose command-not-found and missing-module errors involving Node.js, npm, or bcryptjs.
Diagnose command-not-found and missing-module errors involving Node.js, npm, or bcryptjs.
Module 3
Generate a bcrypt Password Hash Safely
11
Understanding bcrypt Hashing and One-Way Password Protection
Explain what bcrypt hashing does and why a bcrypt hash cannot be decrypted to recover the password.
Explain what bcrypt hashing does and why a bcrypt hash cannot be decrypted to recover the password.
12
Verify bcryptjs Installation Before Requiring It in Node.js
Confirm that bcryptjs is installed in the backend project before requiring it from Node.js.
Confirm that bcryptjs is installed in the backend project before requiring it from Node.js.
13
Hashing a Password with bcryptjs in Node.js
Run a Node.js one-line script that hashes a chosen password with bcryptjs and capture the resulting hash.
Run a Node.js one-line script that hashes a chosen password with bcryptjs and capture the resulting hash.
14
Why Bcrypt Produces Different Hashes for the Same Password
Explain why hashing the same password more than once produces different valid bcrypt hashes.
Explain why hashing the same password more than once produces different valid bcrypt hashes.
15
Protect Passwords from Accidental Exposure
Avoid exposing real passwords through copied commands, screenshots, source control, or shared terminal history.
Avoid exposing real passwords through copied commands, screenshots, source control, or shared terminal history.