Build scalable realtime features


Programmatic push notifications



Read the docs to learn how to use our products


Explore our tutorials to build apps with Pusher products


Reach out to our support team for help and advice

Sign in
Sign up

Build a live score feed Chrome extension

  • Neo Ighodaro

January 31st, 2019
You will need Node installed on your machine.


In this tutorial, we will look into how to build a Chrome extensionand also integrate realtime updates using the Pusher Channels API.

Sometimes, a traditional website isn’t the optimal channel for conveying realtime updates, because the updated event needs to be utilized instantaneously. The process of loading up a new webpage and waiting for it to update with data can be quite inconvenient to the consumer who doesn’t want to have to leave the current tab to retrieve data.

Chrome extensions are basically little websites that add extra functionality to Chrome and can be accessed from all open tabs on the Chrome browser. Under the hood, a Chrome extension is some HTML, CSS, and JavaScript that has access to the JavaScript APIs that Chrome exposes.

What we will build

We will build a simple Chrome extension that displays score updates on an NFL game. We will not key into an API but simulate the scores and cause them to progress randomly. For the sake of this tutorial, we will assume that the game being played is Indianapolis Colts vs Tennessee Titans and the extension will display updates in realtime once it is started.

By the end of this article, we will have built this Chrome extension that triggers Chrome notifications whenever there is an update on the game:

The source code to this tutorial is available here on GitHub.


To follow along with this tutorial, you will need to have the following:

If you have all of the above requirements, we can proceed.

Skip the next section if you already signed up with Pusher and created an application.

Setting up a Pusher account

We will need Pusher to power the realtime updates on the extension so you need to create an account here if you don’t already have one. After signing up, create a new Pusher channels application.

While creating the application, fill in some information about the project. Select Vanilla JS for the frontend tech stack and Node.js for the backend tech. When the application is created, note the application’s credentials; we will need them to integrate Pusher into the extension.

Setting up the Node.js backend

The first thing we want to do here is to create a new folder to house the entire project. Create a new directory called realtime-nfl-scores.

Next, launch your terminal and cd into the directory you just created. In there, create an index.js file. This will be the file that will contain the Node.js code.

Next, Let’s initialize the directory for npm:

    $ npm init -y

The command above will generate a package.json file in the root of the project. Next, lets install some dependencies for the application. These dependencies are:

  • Express - A minimalist web framework for Node.js.
  • Dotenv - A package to load environment variables from a .env file into process.env.

To install them, run the following command in your terminal:

    $ npm install express --save
    $ npm install dotenv --save
    $ npm install pusher --save

Because we have Dotenv installed, we can create a .env file in the root directory of the project and use the environment variables in our code. We will access the variables using process.env. Create a .env file in the root of the project and paste the following contents into the file:

    // File: ./.env

⚠️ Replace PUSHER_* keys with your app credentials.

Open the index.js file and update it with the code below:

    // File: ./index.js
    const express = require("express");
    const app = express();
    const Pusher = require("pusher");


    const pusher = new Pusher({
      appId: process.env.PUSHER_APP_ID,
      key: process.env.PUSHER_KEY,
      secret: process.env.PUSHER_SECRET,
      cluster: process.env.PUSHER_CLUSTER

    const simulate = () => {
      let Colts = {
        name: "Colts",
        score: 0

      let Titan = {
        name: "Titan",
        score: 0

      const generateNumber = () => Math.floor(Math.random() * 2);

      setInterval(() => {
        Colts.score = Colts.score + generateNumber();
        Titan.score = Titan.score + generateNumber();
        pusher.trigger("realtime-updates", "scores", [Colts, Titan]);
      }, 3500);

    app.get("/start", simulate);

    app.listen(3000, () => console.log("Listening on port 3000"));

In the snippet above, we created a new Express application, configured DotEnv and initialized a new Pusher variable. Next, we registered a new instance of the Pusher variable using the variables that we previously stored in the .env file.

We defined a simulate function to generate a random number between 0 and 1 every 3.5 seconds, then trigger a new scores event (sending over the generated data) on the realtime-updates channel.

We defined a single GET endpoint called start and this is the endpoint that’s responsible for starting the generating of pseudo scores and triggering events. Finally, we specified that the server should listen for requests on port 3000.

This is all the code we need for the backend, let’s move on to building the frontend.

Building the frontend

In this section, we are going to start building the Chrome extension. The first thing we want to do is create a separate folder for the extension. Create a new folder called frontend and cd into it in your terminal.

All Chrome extensions require a manifest file. The manifest file tells Chrome everything it needs to know about the extension. Create a manifest.json file inside the extension project directory and paste the following into it:

    // File: ./manifest.json
      "manifest_version": 2,
      "name": "Real-time NFL score",
      "version": "1.0",
      "description": "A simple Chrome extension to simulate the NFL scores in real-time",
      "content_security_policy": "script-src 'self'; object-src 'self'",
      "browser_action": {
        "default_icon": "./img/icon.png",
        "default_popup": "popup.html"
      "permissions": ["notifications", "activeTab"]

Most of the keys in this JSON file are self-explanatory, let's go over the ones that are not:

  • content_security_policy: We register two remote origins that we want the extension to execute scripts from. To learn more about content_security_policy read here.
  • browser_action: We specify what the default icon of the extension is (we will create one shortly) and what HTML page should be displayed when the extension is opened.
  • permissions: We specify in this section that we need to access the activeTab and Notifications.

Setting the default icon

You’ll notice that we specified a path to the default icon in the manifest file but didn’t create the folder or the file yet, so let’s do that now. Create a new folder and call it img. In the img directory, we will save an image (a png) file as icon.png.

You can use any image of your choice! We just want something that looks nice for an extension’s default icon. We have an icon you can use in the repo but it should not be used without permission.

Setting up the UI

In the manifest file, we indicated that an HTML file called popup.html should be displayed when the extension is opened. So, let’s create the file now in the root of the frontend directory and paste the following code into the file:

    <!-- File: ./popup.html -->
    <!DOCTYPE html>
          @import url("");
          body {
            height: 130px;
            width: 260px;
            font-family: "Kosugi Maru", sans-serif;
        <title>NFL score</title>
        <nav class="navbar navbar-dark bg-dark">
          <a class="navbar-brand" id="scores" href="#">Real-time NFL scores </a>
        <div class="container text-center mt-2">
          <div id="score_label"><p id="results">----</p></div>
        <script src=""></script>
        <script src="popup.js"></script>

The code above is an HTML description to display a simple Bootstrap layout for the extension. In the bottom of the code, we linked to two scripts:

  1. pusher.min.js - This is the official Pusher JavaScript SDK.
  2. popup.js - This is a script we will create shortly to handle the extension’s events.

We need the pusher.min.js script to interact with the Pusher API on the client-side, in other words, bind to events and subscribe to channels.

Binding to events and triggering notifications

Let’s create the popup.js file in the root of the frontend directory and paste the following code into the file:

    // File: ./popup.js
    const pusher = new Pusher("PUSHER_APP_KEY", {
      cluster: "PUSHER_APP_CLUSTER",
      encrypted: true

    document.getElementById("scores").addEventListener("click", () => {

    const channel = pusher.subscribe("realtime-updates");

    channel.bind("scores", data => {
      const [teamOne, teamTwo] = data

      document.getElementById("results").innerHTML = `
        <span>${}</span> - ${teamOne.score}<br/>
        <span>${}</span> - ${teamTwo.score}<br />

      notify(teamOne, teamTwo);

    const notify = (first_team, second_team) => {

      if (first_team.score !== 0 && second_team.score !== 0) {
        const notificationId = "notify"

        const options = {
          type:    'basic',
          iconUrl: './img/icon.png',
          title:   `${} vs ${}`,
          message: `There's been a score update on the game between ${} and ${}.`

        chrome.notifications.create(notificationId, options);

Replace the PUSHER_* keys with your credentials from the Pusher dashboard.

In the snippet above, we created a new instance of the Pusher object then we registered a click event listener on the link tag that says Real-time NFL scores.

The event listener further makes a request to http://localhost:3000/start on the Node.js backend server using the fetch API. We want this link tag to be the control for the simulation, so that a click on this link when the extension is open will start the simulation.

Next, we subscribed to the realtime-updates channel and bound to the scores event. In the bind method, we registered a callback that updates the innerHTML of the extension with the scores received from Pusher and lastly, we made a call to the notify function.

The notify function receives two objects, the teams currently playing, and uses them in setting the options object, then it makes a call to Chrome’s Notification API.

Testing out the application

We can easily test the extension by opening the Chrome browser and visiting the address: chrome://extensions:

Once the page opens, turn on the Developer mode option by clicking on the switch by the extreme right of the top of the screen:

Turning on the developer mode made three new options to appear at the top of the screen:

  1. Load unpacked
  2. Pack extension
  3. Update

If we click on the Load unpacked option, we will be asked to select the folder where the unpacked extension lives. So, select the frontend folder.

After selecting the folder, we should be able to see our extension (at the extreme right) with its icon on the extensions tab of the browser:

Now we can start the backend server to test the application. cd to the realtime-nfl-scores project directory and run this command:

    $ node index.js

Once we have the backend server running, we can load up the extension on the Chrome browser, click on the Real-time NFL scores link and watch the realtime updates and notifications flood in:

That’s all. The extension is up and running and we can now see the simulated updates on the game between Indianapolis Colts vs Tennessee Titans.


In this tutorial, we learned how to use Vanilla JavaScript to build a Chrome extension and hit an endpoint on the Node.js web server using the fetch API.

The source code to the application is available on GitHub.

Clone the project repository
  • HTML
  • JavaScript
  • Feeds
  • Node.js
  • Channels


  • Channels
  • Beams

© 2021 Pusher Ltd. All rights reserved.

Pusher Limited is a company registered in England and Wales (No. 07489873) whose registered office is at Eighth Floor 6 New Street Square, New Fetter Lane, London, England, EC4A 3AQ.