Back

@jsparty @acemarke Great discussion about the difficulties with #ESM and I can definitely relate. Ultimately I think a lot of this just comes down to the fact that migrating ecosystems is just hard. I wish there were a clear cause or solution, but there just isn't. I also suspect the "article that explains how to do this right" is impossible because there _isn't_ a single approach which makes every tool happy.

Actually the package format standard and tooling you want actually does exist in the #Angular ecosystem. It's called #APF, Angular Package Format, and it can be generated with `ng-packagr`.

https://angular.io/guide/angular-package-format
https://github.com/ng-packagr/ng-packagr

It's by no means perfect and relies heavily on constraints we enforce on Angular itself (TS versions, browser support, language levels, etc.) But this is a very powerful tool for when we need to make major changes to the Angular ecosystem, such as going ESM-only, which we landed successfully in v13 several years ago.