492304212f
Since we (optionally) support source maps now it's possible that a later PostCSS plugin that *still* does url rewriting might fail to do so correctly because nodes will have preserved source locations in dev builds where before we "pretended" that everything came from the original file. But, because we can't know if such a plugin is present, disabling this behavior when source maps are enabled could cause issues *and* would be a breaking change. I wish everything *could just work* here but realistically we can't know what plugins have run before our PostCSS plugin or what plugins will run after so the best option (I think) we can offer here is to allow users to disable url rewriting at the plugin level. Fixes #16700 |
||
|---|---|---|
| .. | ||
| config.test.ts | ||
| core-as-postcss-plugin.test.ts | ||
| index.test.ts | ||
| multi-root.test.ts | ||
| next.test.ts | ||
| plugins.test.ts | ||
| source.test.ts | ||
| url-rewriting.test.ts | ||