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
Is your feature request related to a problem? Please describe.
First off, thanks for the other changes you made! 🙏
#110 allowed interpolating filenames, but if you add a [hash] or [contenthash] to the file name, you then don’t know the path/url, because it changes with every file change.
Describe the solution you'd like
TL:DR; Other plugins include a path attribute on the imported resource which contains the sprite filename
My usecase is I have a hybrid (icon-heavy) react + .NET app. FE imports the svgs & renders them. I also use WebpackAssetsManifest which outputs a JSON with all emitted resources after the build. This JSON is imported on BE, which might render some html templates and can use this sprite to render an icon.
Describe alternatives you've considered
Removing hash param from name works, but that then might cache the resulting sprite
Additional context
—
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
First off, thanks for the other changes you made! 🙏
#110 allowed interpolating filenames, but if you add a
[hash]
or[contenthash]
to the file name, you then don’t know the path/url, because it changes with every file change.Describe the solution you'd like
TL:DR; Other plugins include a
path
attribute on the imported resource which contains the sprite filenameMy usecase is I have a hybrid (icon-heavy) react + .NET app. FE imports the
svg
s & renders them. I also useWebpackAssetsManifest
which outputs a JSON with all emitted resources after the build. This JSON is imported on BE, which might render some html templates and can use this sprite to render an icon.Describe alternatives you've considered
Removing hash param from name works, but that then might cache the resulting sprite
Additional context
—
The text was updated successfully, but these errors were encountered: