Book Image

Advanced Node.js Development

By : Andrew Mead
2 (1)
Book Image

Advanced Node.js Development

2 (1)
By: Andrew Mead

Overview of this book

Advanced Node.js Development is a practical, project-based book that provides you with all you need to progress as a Node.js developer. Node is a ubiquitous technology on the modern web, and an essential part of any web developer’s toolkit. If you're looking to create real-world Node applications, or you want to switch careers or launch a side-project to generate some extra income, then you're in the right place. This book was written around a single goal: turning you into a professional Node developer capable of developing, testing, and deploying real-world production applications. There's no better time to dive in. According to the 2018 Stack Overflow Survey, Node is in the top ten for back-end popularity and back-end salary. This book is built from the ground up around the latest version of Node.js (version 9.x.x). You'll be learning all the cutting-edge features available only in the latest software versions. This book delivers advanced skills that you need to become a professional Node developer. Along this journey you'll create your own API, you'll build a full real-time web app and create projects that apply the latest Async and Await technologies. Andrew Mead maps everything out for you in this book so that you can learn how to build powerful Node.js projects in a comprehensive, easy-to-follow package designed to get you up and running quickly.
Table of Contents (17 chapters)
Title Page
Copyright and Credits
Packt Upsell
Contributors
Preface
Index

Broadcasting events


Now that we have our custom event listeners and emitters in place, it's time to actually wire up the message system so when one user sends a message to the server, it actually gets sent to every connected user. If I have two tabs open and I emit a createMessage event from one tab, I should see the message arrive in the second one.

To test things locally, we'll be using separate tabs, but the same would work on Heroku with separate browsers on separate networks; as long as everyone has the same URL on their browser, they will be connected, regardless of which machine they're on. Now, for localhost, we obviously don't have the right privilege, but as we deploy to Heroku, which we will be doing in this section, we'll be able to test this out between, say, your phone and the browser running on your machine.

Wiring up the createMessage listener for all users

To get started, we'll update the createMessage listener. Currently, all we do is log the data to the screen. But here,...