Trying to run on older Node?

Nobody has claimed this yet.

Hi,

Thanks for sharing this repo ❤️ - I was really curious to see angular consuming a web component so I cloned that repo and tried to run it. Run into an error - in case anyone is running into it as well - your newer Node version is most likely the cause.
You can try running

```
NODE_OPTIONS='--openssl-legacy-provider' ng serve
```

⠋ Generating browser application bundles (phase: setup)...Compiling @angular/core : es2015 as esm2015
Compiling @angular/common : es2015 as esm2015
Compiling @angular/platform-browser : es2015 as esm2015
Compiling @angular/router : es2015 as esm2015
Compiling @angular/platform-browser-dynamic : es2015 as esm2015
⠹ Generating browser application bundles (phase: building)...Error: error:0308010C:digital envelope routines::unsupported
at new Hash (node:internal/crypto/hash:71:19)
at Object.createHash (node:crypto:133:10)
at BulkUpdateDecorator.hashFactory (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/util/createHash.js:145:18)
at BulkUpdateDecorator.update (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/util/createHash.js:46:50)
at OriginalSource.updateHash (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/node_modules/webpack-sources/lib/OriginalSource.js:104:8)
at NormalModule._initBuildHash (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/NormalModule.js:868:17)
at handleParseResult (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/NormalModule.js:934:10)
at /Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/NormalModule.js:1026:4
at processResult (/Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/NormalModule.js:743:11)
at /Users/xyz/Dev/github/angular-lit-web-components/node_modules/webpack/lib/NormalModule.js:807:5
node:internal/crypto/hash:71
this[kHandle] = new _Hash(algorithm, xofLen);

Reproduce the failure by running `ng serve` and review the reported webpack path and Node crypto error. Compare the behavior with and without `NODE_OPTIONS='--openssl-legacy-provider'`; done should mean the repository can be started successfully on the affected newer Node version without the reported build failure.

Written by the indexing model from the issue text.