🌍 NodeJS · subject

NodeJS Introduction to NodeJS Syllabus

Every chapter and topic of Introduction to NodeJS examined in NodeJS — 2 chapters, 6 topics, plus 50 flashcards written against it.

2Chapters
6Topics
0Sub-topics
~5hEst. first pass
8%Of NodeJS
50Flashcards

Introduction to NodeJS syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Introduction to NodeJS in NodeJS, not a summary of it.

  1. What is NodeJS?

    3 topics
    • Definition and Purpose
    • History and Evolution
    • Key Features
  2. Setting Up NodeJS

    3 topics
    • Installation
    • Node Version Manager (nvm)
    • Verifying Installation

Introduction to NodeJS flashcards for NodeJS

23 of 50 cards from the Introduction to NodeJS deck — real questions with worked answers.

  1. What is Node.js?

    Node.js is an open-source, cross-platform JavaScript runtime environment that executes JavaScript code outside of a web browser, built on Chrome's V8 JavaScript engine.

  2. What is the primary purpose of Node.js?

    To run JavaScript on the server side, enabling developers to build scalable network applications (web servers, APIs, real-time apps) using a single language (JavaScript) for both client and server.

  3. Which JavaScript engine powers Node.js?

    Google's V8 engine (the same engine used in the Chrome browser), which compiles JavaScript directly to native machine code.

  4. What programming language do you write Node.js applications in?

    JavaScript (and also languages that compile to JavaScript, such as TypeScript).

  5. Is Node.js a programming language, a framework, or a runtime?

    It is a runtime environment, not a programming language or a framework. It provides an environment in which JavaScript code can be executed outside the browser.

  6. What I/O model does Node.js use, and why?

    An event-driven, non-blocking (asynchronous) I/O model, which makes it lightweight and efficient for data-intensive, real-time applications that run across distributed devices.

  7. Who created Node.js and in what year?

    Ryan Dahl created Node.js in 2009.

  8. Why was Node.js originally created (the problem it solved)?

    To overcome the limitations of blocking, thread-per-connection web servers (like Apache) by providing a non-blocking, event-driven server capable of handling many concurrent connections efficiently.

  9. On which operating system was Node.js first demonstrated, and at what event?

    It was first demonstrated on Linux (and macOS) by Ryan Dahl at the European JSConf in November 2009.

  10. What company sponsored the early development of Node.js?

    Joyent sponsored and supported the early development of Node.js.

  11. What is npm and when was it introduced?

    npm (Node Package Manager) is the default package manager for Node.js, introduced in 2010, used to install, share, and manage third-party JavaScript packages.

  12. What was the io.js fork and how was it resolved?

    io.js was a 2014 community fork of Node.js created due to governance concerns; it was merged back with Node.js in 2015 under the newly formed Node.js Foundation, unifying the codebases.

  13. What organization currently governs Node.js development?

    The OpenJS Foundation, formed in 2019 by merging the Node.js Foundation and the JS Foundation.

  14. What are the two Node.js release lines, and how do they differ?

    LTS (Long-Term Support) releases, which have even major version numbers and are recommended for production due to stability and extended support; and Current releases, which have the latest features but shorter support.

  15. How do even and odd major version numbers relate to Node.js release lines?

    Even-numbered major versions (e.g., 18, 20, 22) become LTS releases; odd-numbered versions are Current-only and never promoted to LTS.

  16. Name three key features of Node.js.

    (1) Asynchronous and event-driven (non-blocking I/O); (2) Single-threaded with an event loop for high concurrency; (3) Very fast execution due to the V8 engine. (Others: large npm ecosystem, cross-platform, no buffering.)

  17. Is Node.js single-threaded or multi-threaded?

    Node.js runs JavaScript on a single main thread using an event loop, but it offloads certain operations (like file/network I/O) to a background thread pool (via libuv), so it behaves concurrently without creating a thread per request.

  18. What is the event loop in Node.js?

    A mechanism that continuously checks for and dispatches events/callbacks, allowing Node.js to perform non-blocking operations on a single thread by delegating I/O and processing callbacks when operations complete.

  19. What library provides Node.js's asynchronous, non-blocking I/O and event loop?

    libuv, a C library that provides the event loop, thread pool, and cross-platform asynchronous I/O.

  20. Why is Node.js considered highly scalable for I/O-bound applications?

    Because its non-blocking, event-driven model lets a single thread handle thousands of concurrent connections without the overhead of one thread per connection, making it efficient for I/O-bound workloads.

  21. For what type of workload is Node.js NOT well suited?

    CPU-intensive (CPU-bound) tasks, because heavy computation blocks the single main thread and stalls the event loop, delaying all other requests.

  22. What module system did Node.js traditionally use, and what modern standard does it now support?

    Traditionally CommonJS (using require() and module.exports); it now also supports ECMAScript Modules (ESM) using import and export.

  23. In CommonJS (Node.js), what is used to import and export modules?

    require() is used to import a module, and module.exports (or exports) is used to export values from a module.

See more Introduction to NodeJS flashcards →

Planning Introduction to NodeJS for NodeJS

Introduction to NodeJS is about 8% of the NodeJS syllabus by topic count — 6 of 72 topics, spread over 2 chapters. At roughly 45 minutes per topic plus 12 minutes per sub-topic, a first pass runs to about 5 hours.

Work top-down: read the chapter, then tick topics off individually rather than marking the whole chapter done. Sub-topics are where silent gaps hide.

Introduction to NodeJS (NodeJS) FAQ

What is in the NodeJS Introduction to NodeJS syllabus?

Introduction to NodeJS is split into 2 chapters — What is NodeJS? and Setting Up NodeJS, containing 6 topics and 0 sub-topics in total.

How is Introduction to NodeJS structured in the NodeJS syllabus?

2 chapters. Introduction to NodeJS accounts for about 8% of the topics in the whole NodeJS syllabus (6 of 72).

How long should I spend on Introduction to NodeJS for NodeJS?

Budget around 5 hours for a first pass through Introduction to NodeJS — about 45 minutes per topic plus 12 minutes per sub-topic across its 6 topics. Add revision cycles on top.

Are there flashcards for NodeJS Introduction to NodeJS?

Yes — a 50-card Introduction to NodeJS deck. Sample cards are printed on this page, and the full deck is free in the Examius app with spaced repetition scheduling.