3 ms·
Heh... was just in the process of updating my comment with Bower when you replied. I agree that this could work with Bower as the package manager. However, it
by NathanKP 12y ago
Heh... was just in the process of updating my comment with Bower when you replied. I agree that this could work with Bower as the package manager.
However, it would be more convenient if there was a distinction between packages that are designed to be UI components, and packages like AJAX libraries, async, and other logic libraries, which are a better fit for bower.
Distributing the UI components via bower is doable, but it wouldn't be nearly as nice as a dedicated component ecosystem where it is easy to search and discover relevant React components.
- colinramsay 12y agoNot even if bower let you search by component type or some kind of category or tag?
- NathanKP 12y agoThe best interface for a react UI component repository would be something that had information like: * A picture of what the component looks like * How large the component is in KB * Which CSS frameworks it requires or supports * Cross browser support information Bower is a very simple package manager right now with little information about the package beyond its name, a line of descriptive text, and a link to the Github. Overall the experience would be better for React devs to develop a customized package manager interface well suited to the type of packages being delivered. Of course there is nothing stopping UI component creators from distributing their components on both Bower and a React specific package manager, but I think for purposes of discoverability a React specific one would be better suited.
- deleted 12y ago[deleted]
- deleted 12y ago[deleted]