Cleanup and safely update dependencies

Clearly it is not the best practice to leave thousands
of security vulnerabilities in the wild, especially
when there are two "critical" ones with "Remote Arbitrary
Code Execution" capability.

This change updates dependencies safely and fixes
all vulnerabilities above "low" severity.

test.js and its dependencies are removed as there is
no test and it seems that there will never be one. It
can be added back later if tests *are* implemented.

All functions in "npm run" are tested. At the first glance,
there is no issue.

Signed-off-by: Jesse Chan <jc@linux.com>

client/scripts/test.js

@@ -1,28 +0,0 @@
-console.log('There are no tests yet.');
-process.exit(0);
-
-// Do this as the first thing so that any code reading it knows the right env.
-process.env.BABEL_ENV = 'test';
-process.env.NODE_ENV = 'test';
-process.env.BASE_URI = '';
-
-// Makes the script crash on unhandled rejections instead of silently
-// ignoring them. In the future, promise rejections that are not handled will
-// terminate the Node.js process with a non-zero exit code.
-process.on('unhandledRejection', err => {
-  throw err;
-});
-
-// Ensure environment variables are read.
-require('../config/env');
-
-const jest = require('jest');
-
-const argv = process.argv.slice(2);
-
-// Watch unless on CI or in coverage mode
-if (!process.env.CI && argv.indexOf('--coverage') < 0) {
-  argv.push('--watch');
-}
-
-jest.run(argv);

client/scripts/typed-css-modules-loader.js

@@ -1,5 +1,5 @@
 const chalk = require('chalk');
-const DtsCreator = require('typed-css-modules');
+const DtsCreator = require('typed-css-modules').default;
 const prettier = require('../../scripts/prettier');
 
 const creator = new DtsCreator();