-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
"extendDefaultPlugins utility is deprecated" warning #6744
Comments
Instead of
it should instead use
as introduced by (But we need to make sure that the svgo dependency semver range of htmlnano also supports this in every case.) |
@mischnic - I made that change in this branch, and it appears to work fine when I |
(Hopefully) fixes parcel-bundler#6744
(Hopefully) fixes parcel-bundler#6744
(Hopefully) fixes parcel-bundler#6744
(Hopefully) fixes parcel-bundler#6744
Someone know about this issue? I have a personal project and i´m migrating from parcel V1 to V2 and i have this issue Thanks! |
@isanchezd1988 It is resolved in the latest parcel nightly branch.
However, it is just a warning and can ignored. |
🐛 bug report
When running
parcel build
on a project with a no cache,@parcel/optimizer-htmlnano
logs a message that the"extendDefaultPlugins" utility is deprecated.
The error does not appear if you re-build with a warm cache. It looks like this may have been hit by someone else incidentally while debugging #6730 (which is a different issue)🎛 Configuration (.babelrc, package.json, cli command)
package.json:
index.html
🤔 Expected Behavior
Running
yarn build
does not produce deprecation warnings.😯 Current Behavior
When you run
yarn build
on a project with a clean cache, you see this:If you run
yarn build
again with a warm cache, the warning will not appear. To see it again, delete the.parcel-cache
folder.💁 Possible Solution
Use
preset-default
to configure svgo.🔦 Context
There's no problems that I've noticed so far with the build output, but it might break in the future if it's deprecated.
💻 Code Sample
You can repro the issue using this repo
🌍 Your Environment
The text was updated successfully, but these errors were encountered: