Currently, we had to downgrade the Angular dependencies to achieve a successful npm build.
This step was necessary to cut the release and apply the changes across all Angular applications using this release.
However, we will need to update to the correct Angular version eventually.
Additionally, we request the product owner to review changes to custom browser element attributes.
We are also addressing npm build issues by adjusting dependencies.
We also need to fix a lot of the "deprecated" engine warnings.
A corresponding PR will have to be created for tamu-components to address the same issues.
At present, our successful build relies on an older package-lock file provided by Kevin (dated two years ago). These changes, based on this outdated lock file, involve downgrading Angular dependencies and updating specific packages to fix build issues. We must ensure that these adjustments do not interfere with ongoing feature requests or other updates.
Currently, we had to downgrade the Angular dependencies to achieve a successful npm build. This step was necessary to cut the release and apply the changes across all Angular applications using this release. However, we will need to update to the correct Angular version eventually.
Additionally, we request the product owner to review changes to custom browser element attributes. We are also addressing npm build issues by adjusting dependencies.
We also need to fix a lot of the "deprecated" engine warnings.
A corresponding PR will have to be created for tamu-components to address the same issues.
At present, our successful build relies on an older package-lock file provided by Kevin (dated two years ago). These changes, based on this outdated lock file, involve downgrading Angular dependencies and updating specific packages to fix build issues. We must ensure that these adjustments do not interfere with ongoing feature requests or other updates.