I wonder how intuitive the base name is, or if it should be something like common.
base might indicate that it's an entrypoint for the TV kitchen, whereas I suspect common indicates that the contents are common components across the project.
I'm not eager to make this kind of change since it would impact published packages but wanted to raise the concept.
If we did this I think we would want to deprecate the base version of the packages and eventually unpublish them so they're not sitting in our npm org any longer.
Discussion
What do you want to talk about?
I wonder how intuitive the
basename is, or if it should be something likecommon.basemight indicate that it's an entrypoint for the TV kitchen, whereas I suspectcommonindicates that the contents are common components across the project.I'm not eager to make this kind of change since it would impact published packages but wanted to raise the concept.
If we did this I think we would want to deprecate the
baseversion of the packages and eventually unpublish them so they're not sitting in our npm org any longer.Relevant Resources / Research
None.