This repository was archived by the owner on Oct 8, 2024. It is now read-only.
Repository navigation
Use distinct bower.json instead of symlink - #45
Merged
Merged
Conversation
|
👍 |
1 similar comment
Member
|
👍 |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
Fixes #44
Since
v2.0.4we've used a symbolic link forbower.jsonto referencepackage.json. This was done to ease maintenance.Unfortunately, symlinks behave fundamentally differently between Unix and Windows. Bower would read the actual text content of the symlink (
package.json) and report to fail at the first character (p).This restores
bower.json, while also adding an NPM script to make updating it in the future easier.In a future breaking version, we should consider ditching Bower entirely for NPM.
@erikjung @mrgerardorodriguez