If you actually looked at the book you'd see that the significant part of it is looking concepts. For example: why event driven programming is interesting, the

If you actually looked at the book you'd see that the significant part of it is looking concepts. For example: why event driven programming is interesting, the architectural decisions that make Node the way it is, programming style for server-side JavaScript with the event loop, etc. For the APIs I'm taking two approaches, one is looking at the more stable APIs (e.g. http) and showing how to use them at a high level, with a lot of examples and breakdown of best practice. The other is an API listing which will be taken from the core API docs which I'll be helping to improve. That second direct API reference is the one most at risk. To mitigate that I'm using a build script which builds from the current documentation in markdown on Github. That means the ebook releases and updates will use the very latest version of the book. It's possible we might consider using a print on demand model for the physical book which means that the copies on shelves will be as far from out of date as possible. More than that, I'm pretty connected to the Node community, so I'll be aware of any huge changes coming up and be able to work around those for the final print version of the book. Ebooks are easier to update in time to take into account changes.