Node.JS - Revision history

Todd: /* Installing Packages */

2026-10-21T22:38:56Z

Installing Packages

2026-10-21T22:38:12Z

Installing Node.js

2026-10-21T22:36:45Z

Installing Node.js

2026-10-21T22:34:37Z

Enabling ES Modules (important!)

2026-10-21T22:34:24Z

Enabling ES Modules (important!)

2026-10-21T22:33:58Z

Modern Node style: Promises and async/await

2026-03-04T18:46:51Z

Node.js Conventions

2026-03-04T18:14:38Z

Installing Node.js

2026-03-02T18:35:41Z

Node.js Security

2026-03-01T13:31:28Z

@@ Line 150: / Line 150: @@
 === Installing Packages ===
-In order for the example code below to work, you need the '''mime''' package (it helps map filenames to Content-Type headers). The `mime` package is actively maintained. :contentReference[oaicite:9]{index=9}
+In order for the example code below to work, you need the '''mime''' package (it helps map filenames to Content-Type headers). The `mime` package is actively maintained.
 In the directory where you will save your Node.js file:

@@ Line 87: / Line 87: @@
 </source>
-'''Note:''' As of February 2026, Node 24 is the Active LTS line. Using `nvm install --lts` means you do not have to hardcode a specific major version in the instructions.
+'''Note:''' As of October 2026, Node 24 is the Active LTS line. Using `nvm install --lts` means you do not have to hardcode a specific major version in the instructions.
 == Your First Node.js Application: Hello World ==

@@ Line 75: / Line 75: @@
 == Installing Node.js ==
-We will install Node using '''nvm''' (Node Version Manager). This makes it easy to switch Node versions and consistently use the current LTS version. :contentReference[oaicite:4]{index=4}
+We will install Node using '''nvm''' (Node Version Manager). This makes it easy to switch Node versions and consistently use the current LTS version.
 Run the following commands:
@@ Line 87: / Line 87: @@
 </source>
-'''Note:''' As of February 2026, Node 24 is the Active LTS line. Using `nvm install --lts` means you do not have to hardcode a specific major version in the instructions. :contentReference[oaicite:6]{index=6}
+'''Note:''' As of February 2026, Node 24 is the Active LTS line. Using `nvm install --lts` means you do not have to hardcode a specific major version in the instructions.
 == Your First Node.js Application: Hello World ==

@@ Line 127: / Line 127: @@
+}
 </source>
 If you do not do this, Node may treat `.js` files as CommonJS by default, and `import ...` may fail.

@@ Line 118: / Line 118: @@
 === Enabling ES Modules (important!) ===
-Modern Node supports both the older '''CommonJS''' module system (require) and the newer JavaScript standard '''ES Modules''' (import/export). ES Modules are the direction modern JavaScript has moved (and they match browser JavaScript). :contentReference[oaicite:7]{index=7}
+Modern Node supports both the older '''CommonJS''' module system (require) and the newer JavaScript standard '''ES Modules''' (import/export). ES Modules are the direction modern JavaScript has moved (and they match browser JavaScript).
 To tell Node to treat `.js` files as ES Modules, add this to `package.json` in your project directory:

@@ Line 51: / Line 51: @@
 === Modern Node style: Promises and async/await ===
-Callbacks are still important to understand (they explain why Node "works"), but modern Node code often uses '''Promises''' and '''async/await''' because they make programs easier to read and debug. :contentReference[oaicite:3]{index=3}
+Callbacks are still important to understand (they explain why Node "works"), but modern Node code often uses '''Promises''' and '''async/await''' because they make programs easier to read and debug.
 Conceptually:

@@ Line 249: / Line 249: @@
 $ npm init -y
 </source>
 One nice feature of <code>package.json</code> is that it automatically handles dependencies. For example:

← Older revision		Revision as of 18:35, 2 March 2026
Line 240:		Line 240:

	Just because we're writing in JavaScript doesn't mean we can forget about the security practices you've been learning in CSE 330. XSS is still a problem, as is the use of ''eval'', CSRF attacks, and so on.		Just because we're writing in JavaScript doesn't mean we can forget about the security practices you've been learning in CSE 330. XSS is still a problem, as is the use of ''eval'', CSRF attacks, and so on.
−
−	~~Two links with Node-specific security discussions:~~
−
−	~~# Book from PragProg ($24, 2015): https://pragprog.com/book/kdnodesec/secure-your-node-js-web-application~~
−	~~# Slideshow from a Switzerland Conference on Application Security (2012): http://www.slideshare.net/ASF-WS/asfws-2012-nodejs-security-old-vulnerabilities-in-new-dresses-par-sven-vetsch~~

	== Node.js Conventions ==		== Node.js Conventions ==

← Older revision		Revision as of 13:31, 1 March 2026
Line 276:		Line 276:
	'''Tip:''' Modern npm automatically saves dependencies when you run <code>npm install package-name</code>. The older <code>--save</code> flag is no longer necessary.		'''Tip:''' Modern npm automatically saves dependencies when you run <code>npm install package-name</code>. The older <code>--save</code> flag is no longer necessary.

−	[[Category:Module 7]]	+	[[Category:Module 5]]