> For the complete documentation index, see [llms.txt](https://jianghua-yjhs-organization.gitbook.io/in-depth-understanding-of-node.js-core-ideas-and/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jianghua-yjhs-organization.gitbook.io/in-depth-understanding-of-node.js-core-ideas-and/readme.md). # README ## 《Deep into Node.js》: Core Concepts and Source Code Analysis This book analyzes the source code of Node.js based on node v6.0.0. The source code analysis includes (libuv, v8), and requires a certain level of C and C++ foundation. The source code of Node.js is full of developers' wisdom and the spirit of pursuing the ultimate, including but not limited to: * System architecture * Design patterns * Performance optimization * Tricks This book explains the core concepts of node's asynchronous IO and event loop by analyzing the implementation of node's core modules, helping developers to better use Node.js. By tracing the development issues of the node community, we can explore the changes and evolution of node and learn the design philosophy of node.js. ## Table of content * [Overview](/in-depth-understanding-of-node.js-core-ideas-and/chapter1.md) * [Architecture Overview](/in-depth-understanding-of-node.js-core-ideas-and/chapter1/chapter1-0.md) * [Why libuv](/in-depth-understanding-of-node.js-core-ideas-and/chapter1/chapter1-1.md) * [V8 Concepts](/in-depth-understanding-of-node.js-core-ideas-and/chapter1/chapter2-0.md) * [C++ and JS Interaction](/in-depth-understanding-of-node.js-core-ideas-and/chapter1/chapter2-1.md) * [Starting from Hello World](https://github.com/yjhjstz/deep-into-node/blob/main/chapter1/chapter1-2.md) * [Module Loading](/in-depth-understanding-of-node.js-core-ideas-and/chapter2-2.md) * [Global Object](/in-depth-understanding-of-node.js-core-ideas-and/chapter12-1.md) * [Event Loop](/in-depth-understanding-of-node.js-core-ideas-and/chapter5-1.md) * [Timer Interpretation](/in-depth-understanding-of-node.js-core-ideas-and/chapter3-1.md) * [Yield Magic](/in-depth-understanding-of-node.js-core-ideas-and/chapter3-2.md) * [Buffer](/in-depth-understanding-of-node.js-core-ideas-and/chapter6-1.md) * [Event](/in-depth-understanding-of-node.js-core-ideas-and/chapter7-1.md) * [Domain](/in-depth-understanding-of-node.js-core-ideas-and/chapter13-2.md) * [Stream](/in-depth-understanding-of-node.js-core-ideas-and/chapter8-1.md) * [Net](/in-depth-understanding-of-node.js-core-ideas-and/chapter9.md) * [Socket](/in-depth-understanding-of-node.js-core-ideas-and/chapter9/chapter9-1.md) * [Building Applications](/in-depth-understanding-of-node.js-core-ideas-and/chapter9/chapter9-2.md) * [Encryption](/in-depth-understanding-of-node.js-core-ideas-and/chapter9/chapter9-3.md) * [HTTP](/in-depth-understanding-of-node.js-core-ideas-and/chapter10.md) * [HTTP Server](/in-depth-understanding-of-node.js-core-ideas-and/chapter10/chapter10-1.md) * [HTTP Client](/in-depth-understanding-of-node.js-core-ideas-and/chapter10/chapter10-2.md) * [FS File System](/in-depth-understanding-of-node.js-core-ideas-and/chapter11.md) * [File System](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-2.md) * [File Abstraction](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-1.md) * [IO](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-3.md) * [libuv Selection](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-4.md) * [File IO](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-5.md) * [Fs Essence](/in-depth-understanding-of-node.js-core-ideas-and/chapter11/chapter11-6.md) * [Process](/in-depth-understanding-of-node.js-core-ideas-and/chapter13.md) * [Child Process](/in-depth-understanding-of-node.js-core-ideas-and/chapter13/chapter13-1.md) * [Cluster](/in-depth-understanding-of-node.js-core-ideas-and/chapter13/chapter4-1.md) * [Node.js Pitfalls](/in-depth-understanding-of-node.js-core-ideas-and/chapter14-5.md) * [Others](/in-depth-understanding-of-node.js-core-ideas-and/chapter14.md) * [Node.js & Android](/in-depth-understanding-of-node.js-core-ideas-and/chapter14/chapter14-1.md) * [Node.js & Docker](/in-depth-understanding-of-node.js-core-ideas-and/chapter14/chapter14-2.md) * [Node.js Tuning](/in-depth-understanding-of-node.js-core-ideas-and/chapter14/chapter14-3.md) * [Appendix](/in-depth-understanding-of-node.js-core-ideas-and/chapter14-0.md) This book is copyrighted by the author. Unauthorized reproduction in any form is prohibited. * Contact the author Weibo: * Email: yjhjstz#gmail.com This book is still being written. Welcome readers to discuss **If you think it's good, please buy me a cup of coffee, welcome to Star, submit PR** --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://jianghua-yjhs-organization.gitbook.io/in-depth-understanding-of-node.js-core-ideas-and/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.