You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
bower is making the version property optional in bower.json. While this is inconsistent with npm / package.json, it's not a road block since we can simply stop versioning bower packages. If bower someday decides to allow multiple versions of a package, we can revisit the solution. For now, this should work fine.
We will need to apply a fix in [at least] two places:
where rave crawls for bower packages
where rave normalizes module names
The text was updated successfully, but these errors were encountered:
unscriptable
changed the title
bower packages must be unversioned
Bower packages must be unversioned
Jun 11, 2014
I noticed that you defaulted to "0.0.0" in one of the PRs. I like that this keeps the logic the same. 👍
I was briefly worried about situations wherein a package is a dependency in both npm and bower (e.g. this could happen with a popular package like when.js), but I think this still works out. Closing in favor of your suggestion. Add it to #40?
bower is making the
version
property optional in bower.json. While this is inconsistent with npm / package.json, it's not a road block since we can simply stop versioning bower packages. If bower someday decides to allow multiple versions of a package, we can revisit the solution. For now, this should work fine.We will need to apply a fix in [at least] two places:
The text was updated successfully, but these errors were encountered: