How to categorize a particular library

[knackstedt]

Subject: Proposal for a "Framework Interoperability" or "Cross-Framework" section and repository curation

Problem: Categorization of Angular-React Interoperability Libraries

I'm looking to submit a Pull Request to include a library I've developed, ngx-reactify, which facilitates the use of React components within Angular applications and vice-versa. My library is already in the list but I've added a massive new feature on it and I'm noticing that people can't easily pick it out from this list.

Currently, I'm finding it challenging to categorize this type of library within the existing awesome-angular repository structure. While the "Integrations" section exists, it appears to be quite broad, encompassing a mix of general components and SaaS integrations (e.g., DataDog, Elastic, Sentry).

There are at least two other similar libraries already listed in the awesome-angular README that aim to provide Angular-React compatibility:

• ng-react-bridge
• ngx-react

These libraries, including my own, fall into a unique category of "framework interoperability" or "cross-framework" solutions. Grouping them together would significantly improve the clarity and discoverability of such resources for developers looking to integrate Angular and React.

Proposal: New Section or Refined Category

I propose creating a dedicated section for libraries that enable interoperability between Angular and other frontend frameworks, particularly React. Something along the lines of:

• Framework Interoperability
• Cross-Framework Solutions
• Angular + [Other Framework] Integrations

This would help segment the current "Integrations" section, making it more focused and easier to navigate.

Suggestion for Repository Curation

On a separate note, I've noticed that some linked resources might benefit from a basic review to ensure their quality and prevent potential issues for users. For instance, the example code in the following article leads to a memory leak:

• https://www.gooddata.com/blog/frontend-integration-series-angular/

This is just an observation, but perhaps incorporating a periodic review or a small guideline for resource quality could be beneficial for the awesome-angular repository overall.

Request for Guidance

I'd appreciate any guidance on the best approach for this. Would you be open to a new section, or do you have alternative suggestions for how these Angular-React interoperability libraries could be effectively grouped?

[jdegand]

@knackstedt Limited entries lead to including some things in less than ideal categories. Some libraries definitely can go in multiple categories so it definitely can never be a perfect process. I have been gradually pruning resources and reworking sections. As for the tutorial link, when there is limited information out there, sometimes, it is better than nothing. I am definitely open to adding or removing sections and one possible solution may be to add sub-categories under integrations. I will investigate and try to do something soon.

[jdegand]

@knackstedt Actually, I think the library you wanted to add, ngx-reactify, was already included. I took most of suggestions and finally reworked the repo to match awesome-lint specs (I wasn't aware of this until recently). I think it is greatly improved. You can leave any feedback or additional thoughts.

[knackstedt]

@jdegand That looks much cleaner -- and I know that ngx-reactify was already in the list but a new feature addition made me realize that moving it around might be necessary, as when I first added it all it was capable of was wrapping React components into Angular components. It's now capable of wrapping Angular components into React components, which prompted this issue since I wasn't sure how to categorize that.
I can help out with vetting any projects or documentation for embedding React components in Angular, if you see value in going through that process.

[jdegand]

@knackstedt If you see something worthwhile (React related or otherwise), please raise an issue or PR. Thanks again.