Performance and SEO optimisations

[JSKitty]

Abstract

To improve MPW's size and loading time, this PR employs a bunch of webpack-level and dependency changes, such as:

• Setting webpack to production mode (enables many dist optimisations) for builds.
• Plugging in a CSS minimizer.
• Replacing the bloaty whole lodash import for per-function lodash-es imports.
• For SEO/Indexing purposes: switching the navbar <a> buttons to <span>.

Much of these issues were shown with the help of Lighthouse, in which MPW has quite bad performance and loading times - this PR will dramatically decrease the loading time for MPW.

My current local tests (using production and this PR) show these results:

Production (CSS and JS only)

Pull Request (CSS and JS only)

What does this PR address?

The PR helps address the slow loading times of MPW, by vastly decreasing the app's compiled size and by stripping unused dependency bloat from the app.

What features or improvements were added?

No user-level features, just faster loading! (Which also means less bandwidth usage).

How does this benefit users?

MPW will now load significantly faster, especially notable on slower networks or hosts, this PR also improves SEO and search engine indexing by the boost in performance, and the tweak to the navbar which resolves some indexing issues.

[BreadJS]

I'm all for it! LGTM!

[Liquid369]

tACK 6cfcff7
We absolutely need this the question is nonsensical in the perf increase alone and then SEO we do need to start addressing.
Great start

[Duddino]

Can you commit package.lock.json as well?

Adding this to the config should prevent bn.js to get loaded multiple times

resolve: {
  alias: {
    'bn.js': path.join(__dirname, 'node_modules/bn.js/lib/bn.js'),
  }
},

[Duddino]

tACK, it's perfect now

[Liquid369]

tACK 500ada3

Shoot, just saw, resolve conflicts lol

[JSKitty]

Resolved conflicts, good to go again.

[Duddino]

tACK

[Liquid369]

tACK b3be63b