Update wiredep in web/app/themes/cnh/package.json from ^2.2.2 to 4.0.0 #33
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.
Overview
The following dependencies have been updated by dependencies.io:
wiredep
inweb/app/themes/cnh/package.json
from "^2.2.2" to "4.0.0"Details
wiredep
This dependency is located in
web/app/themes/cnh/package.json
and was updated from "^2.2.2" to "4.0.0".3.0.0
Alert: Breaking changes!
3.0.0 will make some changes which may affect your app. Please read before upgrading.
Testing it out
Breaking changes
REMOVED: Auto-detecting paths outside of a
<!-- bower -->
block.Previously, if your source file included a reference to one of your Bower dependencies outside of your
<!-- bower -->
block, wiredep wouldn't inject it inside of the block. This was originally done to support using Modernizr.js in the<head>
section of your HTML file without it being re-injected in the<body>
. Not only is this no longer Modernizr's recommended practice, but we have since added theexclude
option in wiredep's configuration that would allow you to duplicate this behavior without any magic.REMOVED: Elite dependencies.
Previously, wiredep kept a list of packages that were known to be required before any other scripts. This included jQuery, es5-shim, etc. This was originally done in the very early days of Bower, as packages weren't properly listing their dependencies (if they even had a
bower.json
at all!). Things have come a long way since then, and this should no longer be required. If you are using packages that don't list their dependencies properly, offer them a PR with the correction.ADDED: Support for packages that don't have a
main
.Previously, if one of your dependencies didn't have a
main
file, wiredep wouldn't go through its dependencies to inject theirmain
s. We've since found out this is a common practice for some Polymer packages, and also just makes more sense, so now it doesn't matter if the root component doesn't have amain
. wiredep will continue going through its dependencies.Problems?
If this causes any breakages in your app unrelated to the explanations above, please open an issue.
3.0.1
Patch release to update dependencies to get rid of npm warnings. Functionality should not have changed
We didn't find any content for 4.0.0. Feel free to open an issue at https://github.com/dependencies-io/support to suggest any improvements.