You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 19, 2024. It is now read-only.
When you use cssnext with webpack's css-loader in module mode, url(./file) is transformed to url(file). This is done by postcss-url included in cssnext. Because of this issue, if you use url(./image.png), the css-loader?module gets it as url(image.png) and treats it as a module and searches in moduleDirectories rather than the relative path.
So, with css-loader module mode, I guess it is correct to use { url: false } option in cssnext which is propagated to postcss-url. So can we add a note about this in this repo?
postcss-cssnext do not handle url anymore (cssnext is now postcss-cssnext. cssnext is deprecated.) See postcss-cssnext migration guide http://cssnext.io/postcss/
When you use cssnext with webpack's css-loader in module mode,
url(./file)
is transformed tourl(file)
. This is done by postcss-url included in cssnext. Because of this issue, if you useurl(./image.png)
, the css-loader?module gets it asurl(image.png)
and treats it as a module and searches in moduleDirectories rather than the relative path.So, with css-loader module mode, I guess it is correct to use
{ url: false }
option in cssnext which is propagated to postcss-url. So can we add a note about this in this repo?Related issues and discussions:
The text was updated successfully, but these errors were encountered: