Custom Node.js Server with the following features

• Seamless WS Support
• Plugin support
• Hot Reloading of routes
• Full async support

Add working jest testing suite for components

The following changes configure the environment for jest testing

Change package.json to exclude tests from nodemon, add a testing script and prevent jest from transforming files via babel

 "scripts": {
    "dev": "cross-env NODE_ENV=development nodemon --exec babel-node src/server/server.js",
    "format": "prettier --write \"./**/*.{js,jsx,json}\"",
+    "test": "jest"
  },
+  "nodemonConfig": {
+    "verbose": false,
+    "ignore": [
+      "tests/*"
+    ]
+  },
+  "jest": {
+    "transform": {}
+  }

An example test would look like the following:

In file: tests/routes/users/loginUser.test.js

const fetch = require('node-fetch');
//${process.env.SERVER_URL}:${process.env.SERVER_PORT}
async function loginUser(username, email, password) {
    return await fetch(`http://localhost:3000/user/login`,
        {
            method: 'POST',
            body: {
                username, email, password
            }
        }).then(res => res.json());
}

test(`all null values`, () => {
    return loginUser(null, null, null).then(data => {
        console.log(data);
        expect(data).toStrictEqual({
            message: "Error: Missing required parameter username/email and password"
        });
    })
});

*NOTE: Jest runs files containing the string test in its name

Add Global Route Exception Handling by changing the following in (src/server/modules/routeLoader.js)

function packageMiddle(middle) {
    return async function (req, res, next) {
+        try {
            await middle(req, res);
            if(next) 
                next();
+        } catch(err) {
+            res.status(400).send(err);
+        }
    };
}

Still unsure about having exception handling done globally for each route or having it in each async middleware...

Fixing Chaining can be done by changing the following in (src/server/modules/routeLoader.js)

function packageMiddle(middle) {
    return async function (req, res, next) {
+         await middle(req, res);
-         middle(req, res);
        if(next) 
            next();
    };
}

Better Debugging System

Currently the ronin-starter uses basic console logging for verbose messages such as:

• Initialization/Bootup messages (Server startup)
• Route errors (During runtime)

Since console.log is a synchronous process, large amounts of logging can decrease the performance of the server. Additionally there needs to be a better system to log messages to a file for archival purposes and also in the event of a server failure.

Implementation of a better debugging system is desireable:

Possible Library Inclusions:

• Winston
• Debug

NEEDS BRAINSTORMING 🧠