build(web-client): npm updates, legacy-peer-deps

[PiDelport]

• Follows Routes #15 and Display QR-Code #14

I think this finally gets our npm packages into a more stable state: it looks like the Angular ecosystem isn't really ready for the stricter NPM 7 peer-dependency handling yet, and needs legacy-peer-deps for the time being.

[netlify]

✔️ Deploy Preview for nautilus-wallet ready!

🔨 Explore the source changes: 3f0e31b

🔍 Inspect the deploy log: https://app.netlify.com/sites/nautilus-wallet/deploys/60f050eb3c7e1a0007a7cb0e

😎 Browse the preview: https://deploy-preview-17--nautilus-wallet.netlify.app/

[codecov]

Codecov Report

Merging #17 (3f0e31b) into main (b3e2735) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #17   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            9         9           
  Lines           24        24           
=========================================
  Hits            24        24           

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b3e2735...3f0e31b. Read the comment docs.

[PiDelport]

@jongbonga: Let me know if this looks and works good to you, too?

[jongbonga]

@PiDelport please remind me what exactly breaks > 12.0.4?

[PiDelport]

@jongbonga: That was the breakage we had with build:prod and build-storybook in #8, and partially fixed in ac7bc77: storybookjs/storybook#15227 (comment) narrowed the issue down to this changed, released in @angular-devkit/build-angular 12.0.4:

• fix(@angular-devkit/build-angular): dispose Sass worker resources on Webpack shutdown angular/angular-cli#21045

However, the fix in ac7bc77 required some manual package lock wrangling to avoid Angular subcomponents at different versions pulling in more than one webpack version, which triggers the problems described here:

• TypeError: The 'compilation' argument must be an instance of Compilation angular/angular-cli#20773

(This happens because of Angular subcomponents using hardcoded versions for things like webpack, rather than ranges: in this case, some Angular 12.1.x component(s) pulled in webpack 5.39.1 alongside 5.38.1, which broke the build.)

To fix this more reliably, all of our Angular components must be from the same (or close enough to the same) Angular release, since those form a consistent set that Angular tests and maintains together.

(The reason for using <12.0.4 rather than just 12.0.3 is that not all Angular subcomponents necessarily update their patch versions for every Angular patch release: for example, a bunch of the @angular-eslint packages are still at 12.0.0.)