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
1.21.0 includes a breaking change #3104
Comments
I see. Admittedly, these plugins were using an unofficial API, so technically it is only a breaking change in something we never promised to keep compatible; the proper way to emit assets is to use the file emission API, not mutate the bundle object. I admit though that the file emission API only got powerful enough recently to support arbitrary asset emission, so I guess we will need to add a "fix" to keep supporting this pattern for the 1.x releases, especially considering that important plugins currently depend on it. |
Fix at #3105 |
@lukastaegert thank you for fixing it so quickly. When should we expect the new release ( |
Released now |
How Do We Reproduce?
#3080 introduced
asset.type
breaks all plugins which generate asset usingasset.isAsset
.Expected Behavior
Minor version should backward compatibility。
Actual Behavior
It's breaks many plugins, like rollup-plugin-postcss
The text was updated successfully, but these errors were encountered: