This repository has been archived by the owner on Oct 2, 2021. It is now read-only.
Packages can now be excluded with excludePackages #38
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
In my case I needed to exclude angular from bower and use the npm version instead because of the export support (
import angular from "angular";). I need to keep angular referenced in bower.json to other angular packages like angular-translate, ... Also I have an old grunt build system that need to exist during the migration to webpack.What I propose is a new parameter excludePackages to list all packages that we want to exclude from bower.
Also, there is an issue that could be solve by this PR: #30