Publish to NPM feature

[crcn]

trafficstars

This is a maybe feature - cool idea, but not sure how well this will scale.

TODOS:

• [ ] published packages go under @paperclipui/[package-name]
• [ ] Need to check interface to make sure package isn't introducing breaking changes**
  • [ ] possibly identify changes & make suggestions about semantic versioning
  • [ ] UI diff % meets threshold, possibly suggest minor, major, patch
  • [ ] APIs removed or renamed? Suggest major change
• [ ] No branching - builds need to be incremental.
• [ ] Diffing automatically built-in
• [ ] Need to consider {...spread} props so that logic can attach anything they want to UI components.

In addition to this, we can scan for packages under @paperclipui namespace and display them in a sort-a marketplace