nodeJS.ai

A practical, deep-dive Node.js field guide — static HTML/CSS/JS, no build step, no framework, open source. Built to pair a concept with runnable code and the interview question that actually tests it.

Live structure: index.html is the home page; every topic lives under /pages. Shared chrome (top bar, sidebar file-tree nav, footer, prev/next, copy-to-clipboard) is rendered by js/layout.js from a single NAV array, so adding a page means editing one list, not fourteen files.

Running it locally

No build step, no dependencies. Any static file server works:

git clone https://github.com/joemrnice/nodeJS.ai.git
cd nodeJS.ai
npx serve .
# or just open index.html directly in a browser

Structure

nodeJS.ai/
├─ index.html                      # home page, full section index
├─ css/style.css                    # design system (tokens, layout, components)
├─ js/
│  └─ layout.js                     # nav data + shared chrome renderer
├─ pages/
│  ├─ getting-started.html          # 00 · foundations
│  ├─ modules-esm-commonjs.html
│  ├─ event-loop.html                # 01 · core runtime
│  ├─ streams-buffers.html
│  ├─ file-system-fs.html
│  ├─ http-frameworks.html           # 02 · building services
│  ├─ npm-packages.html
│  ├─ error-handling-debugging.html  # 03 · quality
│  ├─ testing.html
│  ├─ security-performance.html      # 04 · production
│  ├─ deployment-process.html
│  ├─ projects.html                  # 05 · practice
│  └─ interview-questions.html
└─ README.md

Contributing

This repo is meant to be corrected and expanded in public. If you find a gap, a stale API, or a version-specific detail that's changed:

1. Fork and branch.
2. Keep the voice consistent: concept → runnable code → the question an interviewer would actually ask about it.
3. Tag new interview questions with a data-cat matching an existing filter category in interview-questions.html (or propose a new one).
4. Cross-check against the current Node.js LTS docs (nodejs.org/docs) and MDN before submitting — this guide restyles and reframes those sources, it doesn't replace them as the source of truth.
5. Open a PR.

Deploying

It's plain static files, so any static host works as-is:

• GitHub Pages: Settings → Pages → deploy from the main branch, root.
• Netlify / Vercel: point either at this repo with no build command and . as the publish directory.

License

MIT — see LICENSE. Not affiliated with the Node.js Foundation or OpenJS Foundation; this is an independent community reference.