Skip to content
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

Open
kylecordes opened this issue Nov 16, 2017 · 5 comments
Open

Consider replacing homebrew webpack-etc with ng-packagr #34

kylecordes opened this issue Nov 16, 2017 · 5 comments

Comments

@kylecordes
Copy link
Contributor

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.

@StefH
Copy link
Owner

StefH commented Nov 16, 2017

I will take a look, however I cannot promise I switch to this new tool.

@jornare
Copy link

jornare commented Feb 21, 2020

Please take another look, it is not really new anymore :)

@kylecordes
Copy link
Contributor Author

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.

@StefH
Copy link
Owner

StefH commented Feb 25, 2020

@jornare and @kylecordes : can you maybe create a PR ?

@kylecordes
Copy link
Contributor Author

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants