Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update wiredep in web/app/themes/cnh/package.json from ^2.2.2 to 4.0.0 #33

Closed
wants to merge 1 commit into from

Conversation

dependencies[bot]
Copy link
Contributor

@dependencies dependencies bot commented Aug 7, 2018

Overview

The following dependencies have been updated by dependencies.io:

  • wiredep in web/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

$ npm install --save-dev wiredep@3.0.0-beta

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 the exclude 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 their mains. 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 a main. 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.

@josephnle josephnle closed this Aug 18, 2018
@josephnle josephnle deleted the deps/update-808d2827 branch August 18, 2018 19:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants