Add Angular Elements to the "ng g library" compilation's results
- Langage dominant
- TypeScript
- Étoiles
- 27k
- Forks
- 11.8k
- Merge moyen
- 14 h 23 min
- PR mergées (30 j)
- 162
Description
# 🚀 Feature request
### Command (mark with an `x`)
```
- [x] generate
```
### Description
We know that the "ng g library" helps us with the creation of reusable libraries. The components we create into ous libs can be compiled into multiple JS formats (ES2015, ES5, UMD, ...), which is awesome! Thank you CLI team! However, would it be possible to have them compiled into Web Components as well?
### Describe the solution you'd like
I know that Angular Elements assist with the creation of Web Components. However, I was not able to add Elements to the libs created to "ng g library". Nonetheless, rather than adding it manually... it would be amazing if the CLI team could add that capability to the "ng g library" directly... so that this cmd could insert the necessary configuration for the ng-packager to use and automatically build Web Components alongside the ES2105, UMD, and other formats.
### Describe alternatives you've considered
None yet.
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Commencez par examiner le flux de génération de `ng g library` et la manière dont la configuration de ng-packager contrôle les sorties de compilation des bibliothèques. Le travail est terminé lorsque les bibliothèques générées peuvent compiler Angular Elements/Web Components en plus des formats ES2015, ES5, UMD et autres formats existants.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- angular, typescript
- Domaine
- build-system, cli
- Type d'issue
- Fonctionnalité
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100