Popularity
8.7
Stable
Activity
2.5
-
14,964
709
1,838

Description

Bower offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.

Bower runs over Git, and is package-agnostic. A packaged component can be made up of any type of asset, and use any type of transport (e.g., AMD, CommonJS, etc.).

Code Quality Rank: L4
Monthly Downloads: 0
Programming language: JavaScript
License: MIT License
Tags: Package Managers     Bower    
Latest version: v1.8.8

Bower alternatives and similar libraries

Based on the "Package Managers" category.
Alternatively, view Bower alternatives based on common mentions on social networks and blogs.

  • yarn

    9.6 3.9 L3 Bower VS yarn
    The 1.x line is frozen - features and bugfixes now happen on https://github.com/yarnpkg/berry
  • pnpm

    Fast, disk space efficient package manager
  • Revolutionize your code reviews with AI. CodeRabbit offers PR summaries, code walkthroughs, 1-click suggestions, and AST-based analysis. Boost productivity and code quality across all major languages with each PR.
    Promo coderabbit.ai
    CodeRabbit Logo
  • npm

    9.2 2.1 L4 Bower VS npm
    DISCONTINUED. npm is the package manager for javascript.
  • volta

    Volta: JS Toolchains as Code. ⚡
  • component

    DISCONTINUED. Client package management for building better web applications.
  • jspm

    5.5 2.4 L2 Bower VS jspm
    DISCONTINUED. JSPM is an open source project for working with dependency management via import maps in browsers.
  • Duo

    5.3 0.0 L4 Bower VS Duo
    DISCONTINUED. Next-generation package manager that blends the best ideas from Component, Browserify and Go to make organizing and writing front-end code quick and painless.
  • corepack

    Zero-runtime-dependency package acting as bridge between Node projects and their package managers
  • Ender

    3.9 0.0 L5 Bower VS Ender
    DISCONTINUED. the no-library library: open module JavaScript framework
  • volo

    3.9 0.0 L2 Bower VS volo
    Create front end projects from templates, add dependencies, and automate the resulting projects
  • jam

    3.8 0.0 L5 Bower VS jam
    DISCONTINUED. A package manager using a browser-focused and RequireJS compatible repository.
  • spm

    DISCONTINUED. Brand new static package manager.
  • Refraction

    A guard that represents a central point of control in your application

Do you think we are missing an alternative of Bower or a related project?

Add another 'Package Managers' Library

README

Bower - A package manager for the web

Build Backers on Open Collective Sponsors on Open Collective

..psst! While Bower is maintained, we recommend yarn and webpack or parcel for new front-end projects!


Bower offers a generic, unopinionated solution to the problem of front-end package management, while exposing the package dependency model via an API that can be consumed by a more opinionated build stack. There are no system wide dependencies, no dependencies are shared between different apps, and the dependency tree is flat.

Bower runs over Git, and is package-agnostic. A packaged component can be made up of any type of asset, and use any type of transport (e.g., AMD, CommonJS, etc.).

View complete docs on bower.io

View all packages available through Bower's registry.

Install

$ npm install -g bower

Bower depends on Node.js and npm. Also make sure that git is installed as some bower packages require it to be fetched and installed.

Usage

See complete command line reference at bower.io/docs/api/

Installing packages and dependencies

# install dependencies listed in bower.json
$ bower install

# install a package and add it to bower.json
$ bower install <package> --save

# install specific version of a package and add it to bower.json
$ bower install <package>#<version> --save

Using packages

We discourage using bower components statically for performance and security reasons (if component has an upload.php file that is not ignored, that can be easily exploited to do malicious stuff).

The best approach is to process components installed by bower with build tool (like Grunt or gulp), and serve them concatenated or using a module loader (like RequireJS).

Uninstalling packages

To uninstall a locally installed package:

$ bower uninstall <package-name>

prezto and oh-my-zsh users

On prezto or oh-my-zsh, do not forget to alias bower='noglob bower' or bower install jquery\#1.9.1

Never run Bower with sudo

Bower is a user command; there is no need to execute it with superuser permissions.

Windows users

To use Bower on Windows, you must install Git for Windows correctly. Be sure to check the options shown below:

Note that if you use TortoiseGit and if Bower keeps asking for your SSH password, you should add the following environment variable: GIT_SSH - C:\Program Files\TortoiseGit\bin\TortoisePlink.exe. Adjust the TortoisePlink path if needed.

Ubuntu users

To use Bower on Ubuntu, you might need to link nodejs executable to node:

sudo ln -s /usr/bin/nodejs /usr/bin/node

Configuration

Bower can be configured using JSON in a .bowerrc file. Read over available options at bower.io/docs/config.

Support

You can ask questions on following channels in order:

Contributing

We welcome contributions of all kinds from anyone. Please take a moment to review the [guidelines for contributing](CONTRIBUTING.md).

  • Bug reports
  • [Feature requests](CONTRIBUTING.md#features)
  • [Pull requests](CONTRIBUTING.md#pull-requests)

Note that on Windows for tests to pass you need to configure Git before cloning:

git config --global core.autocrlf input

Backers

Support us with a monthly donation and help us continue our activities. [Become a backer]

License

Copyright (c) 2012-present Twitter and other contributors

Licensed under the MIT License


*Note that all licence references and agreements mentioned in the Bower README section above are relevant to that project's source code only.