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
Seems like this plugin is currently doing two things:
Optimizing the SVG with SVGO
Converting it to a JS module and exporting the SVG as a string
The second step makes the plugin un-interoperable with other Rollup plugins that take SVGs as an input.
For example, rollup-plugin-htmlvue takes in SVGs, converts them into a Vue SFC, and lets the Vue plugin then compile it to a JS.
Wondering if this plugin can become more modular by letting the SVG remain a SVG file, and recommending that users that want to import the SVG as a string chain their plugins with something like rollup-plugin-string:
Seems like this plugin is currently doing two things:
The second step makes the plugin un-interoperable with other Rollup plugins that take SVGs as an input.
For example, rollup-plugin-htmlvue takes in SVGs, converts them into a Vue SFC, and lets the Vue plugin then compile it to a JS.
Wondering if this plugin can become more modular by letting the SVG remain a SVG file, and recommending that users that want to import the SVG as a string chain their plugins with something like rollup-plugin-string:
Although my use-case is with Vue.js, I can imagine this being useful for optimizing SVGs that compile to React or Svetle components too.
The text was updated successfully, but these errors were encountered: