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
Important change is resolving logic for url(......).
resolving logic for uls() and import at-rules works the same everywhere, it does not matter whether css modules are enabled (with global and local module) or not. Examples - url('image.png') as require('./image.png'), url('./image.png') as require('./image.png'), url('~module/image.png') as require('module/image.png')
They says if we used assets from webpack aliased path, we should use ~ prefix.
But css-loader v1 can't resolve its path.
Do you have any plan for css-loader v2 ?
Note: Because there is workaround, this issue's priority may not be high.
Following settings don't work.
module.exports={module: {rules: [{test: /\.css$/,loader: 'css-loader',options: {url: ()=>true,// <- keep resolving logic same to css-loader v1},},],},};
The text was updated successfully, but these errors were encountered:
Recently css-loader was updated to v2 with breaking changes.
Important change is resolving logic for
url(......)
.They says if we used assets from webpack aliased path, we should use
~
prefix.But css-loader v1 can't resolve its path.
Do you have any plan for css-loader v2 ?
Note: Because there is workaround, this issue's priority may not be high.Following settings don't work.
The text was updated successfully, but these errors were encountered: