Skip to content

Mention commiting only bower.json #6043

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Dec 31, 2015
Merged

Mention commiting only bower.json #6043

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
1a98bca
Add mention for Bower.json
krikke26 Oct 12, 2015
d701e3d
Rewrite section about bower.json
wouterj Dec 18, 2015
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions cookbook/frontend/bower.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,6 +135,12 @@ For more details, read the article `Checking in front-end dependencies`_.
But, it's very possible that Bower will add a lock feature in the future
(e.g. `bower/bower#1748`_).

If you don't care too much about having *exact* the same versions, you can only
commit the ``bower.json`` file. Running ``bower install`` will give you the
latest versions within the specified version range of each package in
``bower.json``. Using strict version constraints (e.g. ``1.10.*``) is often
enough to ensure only bringing in compatible versions.

.. _Bower: http://bower.io
.. _`Node.js`: https://nodejs.org
.. _BowerPHP: http://bowerphp.org/
Expand Down