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
In my project I'm loading SVGs from ./dist/svg/* and style them by using the ionicon class on the svg tag. This worked fine until [email protected] but [email protected] removed that class in a patch release, rendering my icons in a broken state.
I don't know if this was an accident and should continue to work or if I'm "holding it wrong" and users of the npm package are not supposed to load stuff from ./dist/svg/. I'm hoping for the first option.
I'm not really sure why we ship the SVGs in two different locations, but the icons at dist/ionicons/svg have the correct class that you can use for now. I'll take a closer look and see why we have both distributions.
Current Behavior
In my project I'm loading SVGs from
./dist/svg/*
and style them by using theionicon
class on thesvg
tag. This worked fine until[email protected]
but[email protected]
removed that class in a patch release, rendering my icons in a broken state.This is the PR that introduced the change #1313.
I don't know if this was an accident and should continue to work or if I'm "holding it wrong" and users of the npm package are not supposed to load stuff from
./dist/svg/
. I'm hoping for the first option.Link to SVG from version 7.2.2.:
https://unpkg.com/[email protected]/dist/svg/accessibility-outline.svg
Note
ionicon
class included.Link to SVG from version 7.2.3.:
https://unpkg.com/[email protected]/dist/svg/accessibility-outline.svg
Note
ionicon
class missing.Expected Behavior
All SVG files within
/dist/svg/
include aclass="ionicon"
on their<svg>
tag, like it's been for multiple major versions.Steps to Reproduce
[email protected]
.node_modules/ionicons/dist/svg/*
haveclass="ionicon"
on their<svg>
tag.[email protected]
.<svg>
tag is gone.Code Reproduction URL
No response
Additional Information
No response
The text was updated successfully, but these errors were encountered: