upstream semver matching

[wenzowski]

Considering this package exists to provide a port of the upstream https://github.com/twbs/bootstrap javascript to derby's component system, I propose that this package's release numbering mirror the upstream css major and minor semver numbering, especially since it repackages it.

[wenzowski]

A decision to not repackage css (#23) would affect my opinion on this, and if bootstrap css/less is not redistributed as part of this package, I'll send some PRs that decouple class names so multiple versions of bootstrap can be used with this component. This would reduce the maintenance load associated with keeping this component current, and allow semver matching with derby rather than bootstrap.

Worth noting however, tight coupling with bootstrap version is very common when redistributing:

• django-bootstrap
• twitter-bootstrap-rails
• meteor-bootstrap-3
• twitter-bootstrap-nuget

...so I assume tight semver coupling is what many developers consuming this package will expect if it includes the bootstrap styles.

Note that angular-ui/bootstrap does not redistribute bootstrap css, requiring manual dependency installation.

[wenzowski]

this project needs peerDependencies
lesson: npm is awesome, this approach is probably crap