-
Notifications
You must be signed in to change notification settings - Fork 59
Can't inline SVG in stylesheets #22
Comments
I can confirm this is not working for SVGs in stylesheets. Any updates on this? |
The transformation for data-format might be trivial, but I think it would be a bit hard to know if this (svg-inline) loader is being called from which loader. I assume you using css-loader? |
Yes, I'm using |
I tried looking into how css-loader works with this(svg-inline) loader and there is no way svg-inline can understand where the request is coming from. I though loader contexts would give some meta information but I could not find any (if there is anything, please someone let me know). They also do not allow any queries for While you are having trouble using css-loader + svg-inline I think you can try https://github.com/TrySound/postcss-inline-svg with some tweaked loader configurations. But I have seen a issue css-loader would break some result while using this postcss plugin, so I can't guarantee it works. |
for me, this isn't a bug as the whole point of the loader is to enable 'inline' use i.e. within the html. for previous project where some svg's were still used as background images, we created a separate loader config in webpack and a separate directory for the background svg's e.g. { test: /\.svg$/,
include: [/styles\/icons\/background-svgs/],
loader: 'url-loader' },
{
test: /\.svg$/,
exclude: [/styles\/icons\/background-svgs/],
loader: 'svg-inline'
} |
To make this work, I had to use a {
test: /\.svg$/,
oneOf: [
{
exclude: path.resolve(__dirname, 'images/svg/css-icons/'),
use: 'svg-inline-loader'
},
{
include: path.resolve(__dirname, 'images/svg/css-icons/'),
use: 'file-loader'
},
],
}, |
I'm still experiencing this problem, nothing has changed by this point? |
There's a problem with using this loader in that it makes in impossible to load SVGs in stylesheets.
Would it be possible to change the output format to Data URI for certain file types? I'm thinking something similar to this approach.
The text was updated successfully, but these errors were encountered: