Discussion: Scoped npm package naming
ChristianMurphy opened this issue ยท 2 comments
ChristianMurphy commented
Hey @UW-Madison-DoIT/uportal-home-committers! ๐
I'm excited for the moves to official Apereo naming and to an official Apereo repo. ๐
One thing that could be worth discussing before it is set in stone is the scope package naming convention. ๐ฌ
โจ๏ธ when typing
@uportal/uportal-home
^^^^^^^^^^^^^^^
this feels awkward to type
@uportal/uportal-app-framework
^^^^^^^^^^^^^^^
same here
I'm wondering if we may want to consider @angular
style scoped naming
Where angular cli is @angular/cli
rather than @angular/angular-cli
.
โก๏ธ Meaning uPortals projects would be packaged as
@uportal/home
@uportal/app-framework
Thoughts? ๐ญ
davidmsibley commented
+1 from me. This also would prevent trying to use the un-scoped name 'uportal-app-framework', which we do not own in npm.
ChristianMurphy commented
resolved in #704
Thanks @davidmsibley!