Closed mattrosno closed 5 years ago
stale[bot]
commented
5 years ago We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.
mattrosno
commented
5 years ago Not stale.
stale[bot]
commented
5 years ago We've marked this issue as stale because there hasn't been any activity for a couple of weeks. If there's no further activity on this issue in the next three days then we'll close it. You can keep the conversation going with just a short comment. Thanks for your contributions.
stale[bot]
commented
5 years ago As there's been no activity since this issue was marked as stale, we are auto-closing it.
With vanilla, React, elements, and component packages... that's around ~120 packages. Bring in Angular and Vue and handlebars we're talking ~216 packages. With so many packages, it'd by nice to view them by package type.
What if we had 4 top-level folders of packages:
components- anything that is either a component spec or implementation.core- "super" packages that bundle up all core components per framework.elements- anything that is used in components but not a component.tools- anything that is config or build.I think it'd also be good to present these packages in table "groups" in the root README.md.
If Angular, Vue, etc. are included, they would each get a "core" package and components would live in "components".
If community components are included, we could integrate them into "components" directory and rely on the "carbon" configs in package.json, or we could create a new directory "components-community".