CODEWITHSUNDEEP
bower
Sagivf
Sagivf

Reputation: 705

Bowers .bower.json file version property

bower.json has a property named version. Bower uses tags to manage versions. I'm wondering what is this property uses for then? Does it have to match the committed tag? If not can it cause issues? Is this another way of managing versions? does bower follow this in any way?

Upvotes: 10

Views: 1894

Answers (2)

sheerun
sheerun

Reputation: 1794

Bower currently ignores version from bower.json.

If the version in bower.json doesn't match git tag, you get a warning, and the version entry in generated .bower.json is fixed (version in bower.json stays the same).

Among others that's why bower plugins should consume.bower.json instead bower.json.

You can safely remove version from your bower.json. Bower only respects git tags.

Most probably it won't be used even in the future.

Upvotes: 12

Ray Shan
Ray Shan

Reputation: 1675

You're correct that bower simply uses the git tags available at the git endpoint submitted during bower register. Most of the info in bower.json is currently mainly used for the package's own record keeping, and isn't kept by the bower registry.

The bower team plans to take advantage of the valuable info in bower.json in the future (discussed here).

Upvotes: 1

Related Questions