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
Add documentation on Angular Libraries best practices #42203
Comments
Yes it would be very nice. You can also follow article of @tomastrajan blog https://link.medium.com/2QwTVrOzNgb |
The link seem to point to this issue so here is another one 😉 |
@tomastrajan oh sorry lol, I posted this from mobile :) |
This feature request is now candidate for our backlog! In the next phase, the community has 60 days to upvote. If the request receives more than 20 upvotes, we'll move it to our consideration list. You can find more details about the feature request process in our documentation. |
+1 |
+1 |
We committed a number of changes to the docs about creating libraries in the last three weeks. See https://github.com/angular/angular/commits/master/aio/content/guide/creating-libraries.md Please can you take a look and let us know if this covers the areas you wanted improved so that we can close this issue as resolved? If it does not, please can you list specific items that need to be addressed so that we can action this request. |
Hi @petebacondarwin ! I think there are some more topics that could be explored (in this doc or maybe in a new "advanced concepts in angular libraries" one):
Those are the topics that come to mind here (which are based on some of my struggles refactoring a gigantic Angular library in my company - more of a core frontend library for multiple related apps, instead of just reusable components). Maybe other participants of this issue have some other suggestions! Cheers! |
I would like to add to this: I'm trying to migrate a angular app to a multi project workspace where my library already lives. The errors that I now get inside my library are:
Now this error isn't giving me any useful information and the docs are pretty summary which makes it hard to look for a solution. |
IMHO it'd be nice to add more info/examples about it, instead of just explaining what it is. |
Greetings!
I'm currently working on improvements in the codebase for an Angular Library used in the web apps I work on. When this library was first created, we didn't have a lot of information about libraries, so there are a lot of problems regarding structure and modular approach.
I've been searching for more information on the subject, but I believe the current official documentation on custom libraries is lacking in details, especially concerning best practices for performance (like multiple entry points, configurations and structures). My main source of knowledge on the subject at the moment are some articles on the web and open source repos.
So, the purpose of this issue is to request improvements in the official library documentation, or even some other sources about this subject. I believe this woud be great for the Angular dev community!
Thank you!
The text was updated successfully, but these errors were encountered: