[mythtv] web app build warnings

[Peter Bennett]

On 10/4/23 13:39, Gary Buhrmaster wrote:
> I am not sure the project wants to address this, but
> a quick look at all of the buildbot workers that build
> the web app as part of their build are reporting:
>
>
>
> npm WARN deprecated @npmcli/move-file at 1.1.2: This functionality has
> been moved to @npmcli/fs
> npm WARN deprecated @npmcli/move-file at 2.0.1: This functionality has
> been moved to @npmcli/fs
> npm WARN deprecated source-map-resolve at 0.6.0: See
> https://github.com/lydell/source-map-resolve#deprecated
> npm WARN deprecated sourcemap-codec at 1.4.8: Please use
> @jridgewell/sourcemap-codec instead
> npm WARN deprecated core-js at 3.20.3: core-js@<3.23.3 is no longer
> maintained and not recommended for usage due to the number of issues.
> Because of the V8 engine whims, feature detection in old core-js
> versions could cause a slowdown up to 100x even if nothing is
> polyfilled. Some versions have web compatibility issues. Please,
> upgrade your dependencies to the actual version of core-js.
>
>
>
> I have not looked at the details, but I suspect
> that upgrading the angular base is the way
> forward (at least some of the packages are
> from angular).  This may, or may not, be straightforward
> (looks like the angular base in MythTV may be
> v13..., which is long unsupported, and the current
> version is v16...).  Angular v16 requires nodejs
> v16 or v18, which seems to be available in the
> MythTV officially supported distros per the
> development guidelines.
>
> The angular framework provides guidance
> as to how to move forward, and what to
> watch out for:
>
>     https://update.angular.io/?v=13.0-16.0
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-dev
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org

I attempted to upgrade angular at some point during the last year. 
Everything seemed fine until I ran the application and I was told I did 
not have a license. After investigating it turned out that you can use 
old versions for free but to use a current version required a license 
($$$). So I went back and upgraded to a slightly newer version that we 
had been using, but that was old enough to not need a license. I decided 
to stick with that for the time being.

Peter