-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
Deprecation warning #258
Comments
Same here. |
|
Aha, thanks! To fix that, would some sort of migration path make sense? E.g:
Alternatively, a new configuration key could be given: I think adding the new configuration key is the only way to avoid any breaking changes, but it also adds more configuration options, which is also difficult. I'm happy to put together a pull request for any of these options - which do you think makes the most sense? |
I would like to use |
Just linking this PR since it is related (outdated; possibly incomplete given issues mentioned here earlier): #197 |
hey deprecate message patch node_modules/rollup-plugin-postcss/dist/index.js
to code
to code : ================================================== my rollup version 2.6.1 |
Please use #197 solution or other fix, this warning in watch mode looks extremely bad, it is printed on every rebuild: 🙏 |
The rollup v2 adaptation is still work in progress and will be released soon to resolve this warning. |
It is solved in |
@SASUKE40 It's gone, thank you ❤️ |
My config:
This emits deprecation warning from rollup:
(!) A plugin is directly adding properties to the bundle object in the "generateBundle" hook. This is deprecated and will be removed in a future Rollup version, please use "this.emitFile" instead.
The text was updated successfully, but these errors were encountered: