Open webpack-bot opened 4 years ago
Wip
I would like to work on this issue.
I am currently working, if I am not able to you can take it
I am currently working, if I am not able to you can take it
Okay :)
Plz update documentation It's so baffled ~
Can anyone tell me how to fix this Deprecation Warning?
@Yee1014 @mitchell-frost @jeffin143
Thanks in Advance.
people getting those Error it's produced due to the 3rd party plugins are not being supported/might be deprecated if someone's struggling with offline-plugin might need to take a Look into the link below there are few alternatives if you'd like to consider.
A pull request by @sokra was merged and maintainers requested a documentation change.
See pull request: https://github.com/webpack/webpack/pull/11176
add missing serializers for classes used in test suite
cc @evilebottnawi for terser-webpack-plugin
What kind of change does this PR introduce? feature
Did you add tests for your changes? internal plugins now use the new API
Does this PR introduce a breaking change? yes,
compilation.cache
is deprecated nowWhat needs to be documented once your changes are merged?
compilation.getCache("MyPlugin")
resp.compiler.getCache("MyPlugin")
can be used to get aCacheFacade
, which is a way to access the cache.compilation.getCache
should be preferred ofcompiler.getCache
.Interface of
CacheFacade
see here: https://github.com/webpack/webpack/pull/11176/files#diff-d96ec7ae5bb4a0907779f25ed03acb33There are methods for
get
andstore
and promise variants. There is also agetChildCache(name)
method to get a child cache, and there is agetItemCache(identifier, etag)
to get anItemCacheFacade
which allows to access a single item.The
CacheFacade
also exposesgetLazyHashedEtag
to get etags for hashable objects likeSource
s.