Dropping bower support

[dalelotts]

In an effort to make things simpler to release and maintain, I'm considering dropping bower support.

If you have any tooling whatsoever (grunt, gulp, jshint, eslint, etc), you're probably already using npm to get your dependencies to build your project. If you're not doing this, install node and npm and run npm init in your project.

If you are currently using bower, you would simply need to install angular-bootstrap-datetimepicker via npm. All you would have to do is:

1. Remove angular-bootstrap-datetimepicker from bower.json
2. run npm install --save angular-bootstrap-datetimepicker
3. Change where you're referencing angular-bootstrap-datetimepicker: bower_components/angular-bootstrap-datetimepicker/... now becomes node_modules/aangular-bootstrap-datetimepicker/....

And that's it. Obviously, if you're doing anything creative you may have a few different or other steps. But you should probably just switch to npm entirely anyway (Why We should Stop Using Bower--And How to Do It).

Please comment on this issue if there are any reasons why this won't work for you.

[marknadig]

👍

[dalelotts]

I you need bower support, you can stay on 0.3.15 for now, that way your build will continue to work. If you need a later version you have a couple of options.

1. Use overrides or pluggable-resolvers to get the later version in a way that doesn't cause bower to complain about the missing bower.json.
2. Move to Browserify or Webpack
3. Probably something else that I don't know about. =)

I'll work on accepting a PR to keep bower support I get semantic-release working for a few minor revisions.

Maybe this will help also: https://roots.io/using-bootstrap-with-bower-how-to-override-bower-packages/