What you'll be able to do

By the end of this page you should be able to explain what stays the same when you move from browser JS to Node, what disappears, and what new responsibilities show up — without pretending you finished a Node course in one post.

Previous post: mini project — fetch list UI.

Who this is for

  • People finishing this browser-first series and curious about backends
  • Juniors who saw require or fs and felt whiplash
  • Anyone choosing between "more frontend" and "try Node next"

You can skip deep Node APIs here — this is a bridge map. This opens Phase 13.

Same language, different host

JavaScript still has variables, functions, promises, and modules. The host changes: instead of Chrome/Firefox APIs, Node gives you process, files, and network server tools.

Scenario A — const x = 1 + 2 works in both.

Scenario B — document.querySelector does not exist in core Node — there is no page DOM.

What goes away (browser gifts)

  • document, window, DOM events
  • localStorage as you know it in pages
  • Automatic UI rendering

Scenario A — your todo DOM project is browser-shaped.

Scenario B — a JSON API returns data; some other client draws UI.

What shows up (Node gifts)

  • Running scripts with node app.js
  • Reading files, talking to databases, handling HTTP on the server
  • Installing packages with npm/pnpm (ecosystem habit)

Scenario A — script that renames files on your machine.

Scenario B — small HTTP server that returns JSON for a React app later.

You will meet CommonJS require and ES modules in Node docs — same modular thinking you practiced, with runtime settings to learn on day one of a real Node path.

Mental model: request on a server

Scenario A — browser. User clicks → your JS runs in their machine.

Scenario B — Node API. User's browser sends HTTP → your Node process runs → response goes back. Secrets and database passwords stay on the server side.

Reflective checklist (practice)

  1. List three APIs you used in this series that need a browser.
  2. List three ideas that transfer (async/await, modules, pure functions, tests).
  3. Open Learn's Node.js topic and pick one article to read next week — for example async patterns or error handling.

Mistakes I see a lot

1. Expecting alert or DOM inside Node tutorials.

2. Putting secret keys in frontend then "moving to Node" without actually moving the privileged call.

3. Learning every Node framework name before writing one file that prints Hello and reads one text file.

What to try before the next post

  1. Install Node LTS when you are ready and run node -e "console.log('hi')".
  2. Skim one Node article on Learn without rushing to build a full app.
  3. Keep your browser projects — they still matter.

Next in this series: JavaScript to React — what you already know — how this series maps onto components and state.

Try this next outside the series

The bridge phase is where plain JavaScript turns into framework and backend confidence.

javascripttutorialsdevelopers