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
/pull/62 fixes a crash caused when trying to aggregateAssets but there is no way, beyond parsing the results of res.locals.aggregatedassets for strings starting with <script> and <style> to know whether an asset is inline.
In the current mean.io implementation all strings are wrapped in the header/footer with link and script tags, which fails to handle inline assets.
A more elegant solution than adding a lot of string parsing to the core/system/server/controllers/index.js in mean, may be to create a res.locals.aggregatedassets.header.inline, and footer.inline.
The text was updated successfully, but these errors were encountered:
/pull/62 fixes a crash caused when trying to aggregateAssets but there is no way, beyond parsing the results of res.locals.aggregatedassets for strings starting with <script> and <style> to know whether an asset is inline.
In the current mean.io implementation all strings are wrapped in the header/footer with link and script tags, which fails to handle inline assets.
A more elegant solution than adding a lot of string parsing to the core/system/server/controllers/index.js in mean, may be to create a res.locals.aggregatedassets.header.inline, and footer.inline.
The text was updated successfully, but these errors were encountered: