Open Quentigus opened 1 year ago
Any update on angular 14 support, now that angular 15 is out for a month? :grin:
Should we fork and provide a PR? Or is anybody working on that already?
Also looking for this, wanting to update my app to Angular 15 and this is blocking now.
is anybody working on that already as angular 16 is out now and it doesn't even support angular 14?
Thanks to @rnsoon for providing PR #475 and for @scttcper for merging it.
But unfortunately there's still a few problems with it. Because this issue wasn't actually finished, I'll just comment that here in trying to get this forward. In fact, we are looking for angular 16 support, before 17 will be released soon - so let's try to clean up loose ends here first before starting over with those 🙈
package.json
:
build
step of the release job, which is an ng-packagr
command:
ng-packagr -p src/lib/package.json
Building Angular Package
Configuration doesn't match the required schema.
Data path "" must NOT have additional properties (name).
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
Error: Process completed with exit code 1.
ng-packagr
configuration location in the package.json. This way of providing ng-packagr
configuration within an ngPackage
property in the package.json
was valid with the previous versions up to v13
, but is a breaking change in the migration to v14
. The CHANGELOG
states:
package.json
is not longer a valid method to configureng-packagr
. Useng-package.json
instead.
ng-package.json
file should be enough to fix this, and get the v14 release built.README.md
wasn't updated to list the new version in the angular compatibility table. Or is this typically done after semantic-release has been performed, on main
branch @scttcper?Should I try to come up with an MR for this, or do you want to follow up with this @rnsoon ?
@sambernet yeah if you have time to make a pull request
@sambernet apologies for the belated response. i'm doing a PR on the ng-package fix. @scttcper re README, should i update the compatibility table to angular 14? or you prefer doing it after creating the ngx14 release?
I'm submitting a ...
[ ] bug report
[X] feature request
[ ] question about the decisions made in the repository
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
What is the expected behavior? Upgrade angulartics to Angular 14
What is the motivation / use case for changing the behavior?
Environment: Enterprise
please run the following and copy the output