Fix bower.json main declaration #168
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
+1 |
1 similar comment
|
👍 |
|
👍 It breaks wiredep too, and probably every tool which conforms to the Bower specification. |
|
This also seems to fix a couple of outstanding issues. Thank you! |
rsandor
added a commit
that referenced
this pull request
Oct 4, 2015
Fix bower.json main declaration
This was referenced Oct 4, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
maindeclaration inbower.jsoncurrently uses absolute paths for some reason, which breaks major bower tools such as main-bower-files.This PR removes the initial path slash, as recommended in the bower.json spec.