-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider replacing homebrew webpack-etc with ng-packagr #34
Comments
I will take a look, however I cannot promise I switch to this new tool. |
Please take another look, it is not really new anymore :) |
I've not been keeping close track either: is it even still necessary to call ng-packagr directly, or is the library support sufficiently complete in Angular CLI? Regardless though, homebrew packaging is even less necessary now than it was in 2017. |
@jornare and @kylecordes : can you maybe create a PR ? |
Unfortunately it's been a couple of years since I've used OData, so I don’t have the occasion to divert effort in this direction today, sorry! |
https://github.com/dherges/ng-packagr
This is a very slick tool, which automates packing up an Angular-compatible library for maximum compatibility with CLI and other build tools, as well as direct (UMD) execution.
I suggest this as a better alternative to homegrown script setups inside a library - you generally get a more compatible, compliant library, with less code/config/work.
The text was updated successfully, but these errors were encountered: