Conversation
~ use same angular version in base package.json ~ update yarn lock for angular package changes
~ run (full) yarn install
~ update ng-packagr to matching angular version (v21) ~ update typescript to 5.9.3 (angular require >5.9) ~ update yarn lock
+ create cjs tsconfig ~ use cjs tsconfig for cjs build
~ fix ng-package config + create build script for generating angular build ~ add angular build to full build
|
Had 2 questions while working on this:
|
~ use node 20 for ci (min required for angular 21)
~ revert used angular version back to v17 ~ revert other related packages back ~ ensure compatible typescript version is used
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. Latest deployment of this branch, based on commit d43e167:
|
|
Lowered the version back to v17 (how it was previous) to keep the same compatibility and prevent breaking changes for now. There should be a plan about when framework versions are updated. v17 is very old (not supported anymore) and limit the usage of angular features (might have some incompatibilities with newer version in the future). |
|
I'm happy to bump to a more recent angular version, if it's breaking then we can release under a major version tag. |
- remove cjs & (manual) esm build configs - remove non angular build scripts - remove build bundle script (part of angular building) - remove not relevant package.json entries
Sounds good - i prepare the APF only build for now and we will wait till v5 with changing angular to min v21 |
~ use partial build mode for better compatibility with different angular versions - remove left over rollup script
|
PR is ready to merge @mathuo feel free to ask for any assistance |
The angular packages lack all angular metadata. Its compiled as regular typescript project.
This PR add an angular build (using ng-packagr) that includes all required metadata for direct usage in angular projects.
Changes: