concept bower component in category javascript

appears as: Bower components
Front-End Tooling with Gulp, Bower, and Yeoman

This is an excerpt from Manning's book Front-End Tooling with Gulp, Bower, and Yeoman.

The following two sections describe the most common JavaScript module patterns. Using modules isn’t necessarily required to create Bower components, but it allows you to better structure your code and integrate it well with existing applications. Because the focus of this chapter is to make the reuse of your JavaScript code as easy as possible, module patterns are not only a recommendation but a must.

Bower’s architecture is geared toward being completely open source. The registry as well as most of the components are publicly available. Even the documentation states that Bower components should be available for everybody—meaning not in hidden or private Git repositories—once you put them in Bower’s public registry. This might not always be the best place for your components. Your company’s policy might prohibit publishing them in the wild, or your component might contain confidential data that nobody else is allowed to see.