Table of Contents for
Node.js 8 the Right Way

Version ebook / Retour

Cover image for bash Cookbook, 2nd Edition Node.js 8 the Right Way by Jim Wilson Published by Pragmatic Bookshelf, 2018
  1. Title Page
  2. Node.js 8 the Right Way
  3. Node.js 8 the Right Way
  4. Node.js 8 the Right Way
  5. Node.js 8 the Right Way
  6.  Acknowledgments
  7.  Preface
  8. Why Node.js the Right Way?
  9. What’s in This Book
  10. What This Book Is Not
  11. Code Examples and Conventions
  12. Online Resources
  13. Part I. Getting Up to Speed on Node.js 8
  14. 1. Getting Started
  15. Thinking Beyond the web
  16. Node.js’s Niche
  17. How Node.js Applications Work
  18. Aspects of Node.js Development
  19. Installing Node.js
  20. 2. Wrangling the File System
  21. Programming for the Node.js Event Loop
  22. Spawning a Child Process
  23. Capturing Data from an EventEmitter
  24. Reading and Writing Files Asynchronously
  25. The Two Phases of a Node.js Program
  26. Wrapping Up
  27. 3. Networking with Sockets
  28. Listening for Socket Connections
  29. Implementing a Messaging Protocol
  30. Creating Socket Client Connections
  31. Testing Network Application Functionality
  32. Extending Core Classes in Custom Modules
  33. Developing Unit Tests with Mocha
  34. Wrapping Up
  35. 4. Connecting Robust Microservices
  36. Installing ØMQ
  37. Publishing and Subscribing to Messages
  38. Responding to Requests
  39. Routing and Dealing Messages
  40. Clustering Node.js Processes
  41. Pushing and Pulling Messages
  42. Wrapping Up
  43. Node.js 8 the Right Way
  44. Part II. Working with Data
  45. 5. Transforming Data and Testing Continuously
  46. Procuring External Data
  47. Behavior-Driven Development with Mocha and Chai
  48. Extracting Data from XML with Cheerio
  49. Processing Data Files Sequentially
  50. Debugging Tests with Chrome DevTools
  51. Wrapping Up
  52. 6. Commanding Databases
  53. Introducing Elasticsearch
  54. Creating a Command-Line Program in Node.js with Commander
  55. Using request to Fetch JSON over HTTP
  56. Shaping JSON with jq
  57. Inserting Elasticsearch Documents in Bulk
  58. Implementing an Elasticsearch Query Command
  59. Wrapping Up
  60. Node.js 8 the Right Way
  61. Part III. Creating an Application from the Ground Up
  62. 7. Developing RESTful Web Services
  63. Advantages of Express
  64. Serving APIs with Express
  65. Writing Modular Express Services
  66. Keeping Services Running with nodemon
  67. Adding Search APIs
  68. Simplifying Code Flows with Promises
  69. Manipulating Documents RESTfully
  70. Emulating Synchronous Style with async and await
  71. Providing an Async Handler Function to Express
  72. Wrapping Up
  73. 8. Creating a Beautiful User Experience
  74. Getting Started with webpack
  75. Generating Your First webpack Bundle
  76. Sprucing Up Your UI with Bootstrap
  77. Bringing in Bootstrap JavaScript and jQuery
  78. Transpiling with TypeScript
  79. Templating HTML with Handlebars
  80. Implementing hashChange Navigation
  81. Listing Objects in a View
  82. Saving Data with a Form
  83. Wrapping Up
  84. 9. Fortifying Your Application
  85. Setting Up the Initial Project
  86. Managing User Sessions in Express
  87. Adding Authentication UI Elements
  88. Setting Up Passport
  89. Authenticating with Facebook, Twitter, and Google
  90. Composing an Express Router
  91. Bringing in the Book Bundle UI
  92. Serving in Production
  93. Wrapping Up
  94. Node.js 8 the Right Way
  95. 10. BONUS: Developing Flows with Node-RED
  96. Setting Up Node-RED
  97. Securing Node-RED
  98. Developing a Node-RED Flow
  99. Creating HTTP APIs with Node-RED
  100. Handling Errors in Node-RED Flows
  101. Wrapping Up
  102. A1. Setting Up Angular
  103. A2. Setting Up React
  104. Node.js 8 the Right Way

Setting Up Node-RED

To begin, create a directory called nodered to house your Node-RED-based code. Then open a terminal to this directory and create an initial package.json.

​ ​$ ​​npm​​ ​​init​​ ​​-y​

Next, install the node-red package locally.

​ ​$ ​​npm​​ ​​install​​ ​​--save​​ ​​--save-exact​​ ​​node-red@0.16.2​

Then open your package.json in a text editor and add a start script to the scripts section like so:

​  ​"scripts"​: {
» ​"start"​: ​"node-red -v -u ./config -f ./config/flows.json"​,
​  ​"test"​: ​"echo ​​\"​​Error: no test specified​​\"​​ && exit 1"​
​  },

Here we’re specifying a couple of command-line arguments to the node-red command. The -v flag turns on verbose mode. The -u flag is short for --userDir and specifies a path to a directory to store configuration information.

The -f flag points to a JSON file that will contain our flows. In Node-RED, a flow is a program that directs events as they flow through a network of nodes.

You’ll be working with flows a lot in this chapter. To begin, run npm start now:

​ ​$ ​​npm​​ ​​start​
​ 
​ > nodered@1.0.0 start ./code/nodered
​ > node-red -v -u ./config -f ./config/flows.json
​ 
​ 19 Jun 04:34:00 - [info]
​ 
​ Welcome to Node-RED
​ ===================
​ 
​ 19 Jun 04:34:00 - [info] Node-RED version: v0.16.2
​ 19 Jun 04:34:00 - [info] Node.js version: v8.1.0
​ 19 Jun 04:34:00 - [info] Linux 4.4.0-79-generic x64 LE
​ 19 Jun 04:34:00 - [info] Loading palette nodes
​ 19 Jun 04:34:01 - [warn] ------------------------------------------------------
​ 19 Jun 04:34:01 - [warn] [rpi-gpio] Info : Ignoring Raspberry Pi specific node
​ 19 Jun 04:34:01 - [warn] ------------------------------------------------------
​ 19 Jun 04:34:01 - [info] Settings file : ./code/nodered/config/settings.js
​ 19 Jun 04:34:01 - [info] User directory : ./code/nodered/config
​ 19 Jun 04:34:01 - [info] Flows file : ./code/nodered/config/flows.json
​ 19 Jun 04:34:01 - [info] Server now running at http://127.0.0.1:1880/
​ 19 Jun 04:34:01 - [info] Starting flows
​ 19 Jun 04:34:01 - [info] Started flows

Toward the end of the output, it’ll inform you that the server is listening on port 1880. If you open http://localhost:1880 in a browser you should see something like this:

images/node-red-initial.png

If you see this, great! Back in your terminal, use Ctrl-C to shut down the server. Next we’ll set up some security around Node-RED.