Closed eshimischi closed 7 years ago
@eshimischi did you find a solution to this?
@razagill nope!! i just commented the line :
`resolve-url-loader?${sourceMapQueryStr}`
i suppose that this is really a problem or with webpack or resolve module itself, tried to find the solution around the code
with no success
@eshimischi Thanks, unfortunately I'm using bootstrap-loader so can't comment the usage. Hopefully we'll get a solution soon.
Please take a look at this comment as it may be relevant.
I presume there are breaking changes with Webpack 2 but I have not had a chance to look into it.
I am not dog-fooding this loader right no so any assistance is appreciated.
A possible workaround for now:
Update line 36ff
var loader = this,
filePath = loader.context,
outputPath = this._compilation.outputOptions.path,
contextPath = this._compilation.options.context;
Using _compilation is considered hacky but at least mentioned in the documentation.
At least this works for now.
@aloker wow! thanks, yes indeed it works now!
Instead of modifing the code you can use
new webpack.LoaderOptionsPlugin({
options: {
context: path.join(__dirname, 'src'),
output: {
path: path.join(__dirname, 'www')
}
}
})
This LoaderOptionsPlugin
simulates the options which where previously given to the plugin via loader.options
.
@mlegenhausen yes, its much much better! appreciate your tip!
@mlegenhausen good! thanks!
It looks like no release was deployed after this fix. Could a beta be released so we don't have to monkey patch this every time?
The preferred workaround would be loader-options-plugin.
Unless the code change is compatible with webpack 1.
i have troubles with resolve-url-loader (1.6.0) and webpack2.1.0.beta25 my webpack.config.js:
package.json:
Asked the same question webpack/webpack#issuecomment-248894366