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
A recent commit moved the svg-sprite to use an externally referenced file, great for caching. However for SVG sandboxing reasons, that means the sprite demo page can only be tested when served from http:// or https://, not from file://.
Can we leverage Node here, so that when you run npm start not only does it build changes when you make them, but it serves results on something like http://127.0.0.1:5000?
The text was updated successfully, but these errors were encountered:
A recent commit moved the svg-sprite to use an externally referenced file, great for caching. However for SVG sandboxing reasons, that means the sprite demo page can only be tested when served from
http://
orhttps://
, not fromfile://
.Can we leverage Node here, so that when you run
npm start
not only does it build changes when you make them, but it serves results on something like http://127.0.0.1:5000?The text was updated successfully, but these errors were encountered: