concept file system in category javascript
appears as: file system, file systems

This is an excerpt from Manning's book Front-End Tooling with Gulp, Bower, and Yeoman.
For tooling, one of the most crucial points lies in the Node.js core layer. Node.js provides functionality that’s close to the operating system. Most of this functionality works with the file system. With the ability to navigate the file system, read files, and operate on the data of those files, Node.js is a perfect environment for writing tools that transform source code into deployment-ready bundles.
File watch processes constantly poll the file system to see if something on the hard disk has changed. Because Gulp is all about transforming files from one state into another, it just makes sense to include this feature in Gulp’s API.
Figure 9.4. Contrary to the asynchronous nature of AMD, CommonJS modules directly provide the exposed functionality from a module, allowing developers to use them in a synchronous manner. Each arrow can be read as a load but not over the network, more from memory or the file system. This access is quick and rarely stalls.
![]()