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 dependency favicons-webpack-plugin to v3 #114

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 2, 2020

This PR contains the following updates:

Package Type Update Change
favicons-webpack-plugin devDependencies major 0.0.9 -> 3.0.1

Release Notes

jantimon/favicons-webpack-plugin

v3.0.1

Compare Source

v3.0.0

Compare Source

⚠ BREAKING CHANGES
  • remove "force" inject option
  • drop support for Webpack v3 and html-webpack-plugin v3
Features
  • add support for html-webpack-plugin v4 (395fc09)
Bug Fixes
  • remove "force" inject option (15bab27)

v2.1.0

Compare Source

⚠ BREAKING CHANGES
  • remove "force" inject option
  • drop support for Webpack v3 and html-webpack-plugin v3
Features
  • add support for html-webpack-plugin v4 (395fc09)
Bug Fixes
  • remove "force" inject option (15bab27)

v2.0.0

Compare Source

Features

v1.0.2

Compare Source

⚠ BREAKING CHANGES
  • an empty string public path will no longer fallback to a slash
  • drop support for node versions < 8 to be able to upgrade favicons
Features
  • allow setting public path to an empty string (b3a5eb3)
Bug Fixes
  • remove unused contentHash (b48697f)

  • upgrade to new favicons version (7c86a6c)

1.0.2 (2019-09-06)
Bug Fixes
1.0.1 (2019-08-16)
Bug Fixes

v1.0.1

Compare Source

v1.0.0

Compare Source

⚠ BREAKING CHANGES
  • Require Node 6 is or newer
  • align with webpack 4 and drop support for node < 6 (e41a990)
  • prefixes are always treated as a directory path
  • remove -[hash] from default prefix
  • by default only a subset of icons is generated in development
Bug Fixes
  • always treat prefix as a directory path (17aabba)
  • avoid failing if html-webpack-plugin isn't installed (1c0ee82)
  • broken links in content meta tags and browserconfig.xml (51bd1f8)
  • do not interpolate empty prefix (9e197f1)
  • do not rely on html-webpack-plugin's internals (9f166a7)
  • handle author as object in package.json (06da1f8)
  • invalidate cache when changing publicPath (29c9902)
  • set SingleEntryPlugin name (15c4a1a)
  • workaround issues with libxml (d23aea5)
  • update favicons to version 5.0.0 (3737fa3)
Features
  • add inject force option to overrule the html-webpack-plugin favicon option (73b51a1)
  • add light mode during development (47986be)
  • add support for html-webpack-plugin 4.x (94ead15)
  • add support for Webpack 4 (9db88ee)
  • add zero-config mode (793a840)
  • added compatibility for new webpack 4 .hooks mode (5ab0bb8)
  • allow skipping specific instances of html-webpack-plugin (d554946)
  • allow to specify a custom output paths (0755161)
  • cache assets using cache-loader (f2758ca)
  • change the default output prefix to assets (99a7310)
  • expose all options of the favicons npm package (ca4b6e9)
  • give the user more options to specifiy where to inject html (c8a4767)
  • make cache directory configurable (43a5aef)
  • remove -[hash] from default prefix (fc0eb3e)
  • the generated [hash] now is based on the current favicon-webpack-plugin version (ccfea37)

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or if you tick the rebase/retry checkbox below.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/favicons-webpack-plugin-3.x branch from 1f0eb73 to 12a10b6 Compare January 29, 2020 08:02
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.

1 participant