Utilities for Everyday Node.js Development
One of the things which makes working with Node fundamentally different from other server-side scripting languages is the functional paradigm provided by JavaScript, which structurally allows for asynchronous, non-blocking transactions through the use of callbacks. What this means is instead of executing a script from beginning to end, Node is always running, with listeners attached to functions ready to do our bidding.
Node does not force you into an architecture, nor does it offer a firm opinion outside of providing JavaScript as a connector between file systems, operating systems, and the internet at large. This interconnection is the core of what Node provides, supplanted by thousands of community written modules: the Node 'ecosystem'.
2 Node Modules
Node modules are written in JavaScript and compiled at runtime, which offers developers the ability to see how modules work, evaluate differing development practices, and diagnose the inevitable bugs that show up. Due to their modular implementation, Node modules don't especially need to be compatible with each other. Several standards, such as Express and Connect, have established a common API to handle common problems, so there are many modules that offer Express compatibility, or use Express as part of their core functionality.
Node modules provide an interchangeable extensibility that is important to get comfortable with; we'll dive into npm first so you can find and utilize modules for your project. At the end of the day, much of what Node developers wrangle with are event callbacks and object manipulation, so we will also explore the async and lodash modules which make these two tasks much easier.
Read full article from Utilities for Everyday Node.js Development
No comments:
Post a Comment