Releases: taptapship/wiredep
v4.0.0
This is a major release due to the BC listed below.
Updated lodash to 4x. Hopefully there are no breaking changes from that. Tests say there aren't.
BREAKING CHANGE: ok not really, not yet but its the start of one. wiredep-cli will no longer be included as part of this npm package in the next major version. It is still being included in this version as a dependency just in case.
v3.0.1
Patch release to update dependencies to get rid of npm warnings. Functionality should not have changed
v3.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-betaBreaking 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.
v3.0.0-beta
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-betaBreaking 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.
Stylus support, better style matching, and events
v1.7.0
v1.6.0
CLI usage now supported!
v1.5.0
v1.3.0
- default support for less
0.4.0
exclude dependencies!