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
I would be great if we could produce different output files for each engine and bundle those with the engine's vendor bundle and of course, the common files can go with the app's bundle.
The text was updated successfully, but these errors were encountered:
Recently I worked on an engine that uses svg-jar using the symbols strategy. The only way I could get svg-jar to work in an engine was to include the path to the engine's SVG's files in thesvgJar configuration of the host apps ember-cli-build.js file. Without this configuration in the host app, the symbols would not be included and injected into the app's index.html.
I tried to configure svgJar in the engine, which did output a symbols.svg file, however, it's not loaded. Engines use ember-asset-loader to load assets, such as JS and CSS. In order to load symbols.svg, I think a SVG loader must be "registered" with the asset-loader service and manifestOptions.supportedTypes must include svg. I need to dig further to determine where I can configure the manifestOptions in an engine.
Also, the engine's symbols.svg file isn't de-dupped with the one the host app outputs. There's a chance for name collisions, as well as an increase in file sizes.
I would be great if we could produce different output files for each engine and bundle those with the engine's vendor bundle and of course, the common files can go with the app's bundle.
The text was updated successfully, but these errors were encountered: