-
-
Notifications
You must be signed in to change notification settings - Fork 608
Respect exclude option when handling url #779
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
Comments
@rodfersou please use |
@evilebottnawi here you are https://github.com/rodfersou/exclude-in-url just run: $ npm install
$ npm run debug and the error will happen |
I tried to use |
@rodfersou yep, it is impossible right now, we prepare |
@evilebottnawi great, I look forward to it |
Thank you very much! |
@evilebottnawi could you please provide an example on how to make this feature work? I just updated the version (in the same PR mentionated) and still get a traceback. |
Okay, I could figure out what was missing, but still for me looks like the result of the function should be inverted to keep in mind the same behavior when it is a boolean.. {
test: /\.scss$/,
use: ExtractTextPlugin.extract({
fallback: 'style-loader',
use: [
{
loader: 'css-loader',
options: {
url: (url, resourcePath) => /\+\+resource\+\+/.test(url)
}
},
'postcss-loader',
'sass-loader'
]
}),
}, |
thank you very much |
@rodfersou can you open issue? |
Is it possible to respect exclude option when handling url?
I have a specific use case, in our CMS an url that has '++resource++' inside should be considered external image. This is my current configuration:
But the url handling is not respecting this configuration, and throw this traceback:
The text was updated successfully, but these errors were encountered: