Bug Report: svg file of "vuestorefront" not exist.

[mztnnrt]

vuestorefront SVG is not exist, but devicons.json is written about it

devicon/devicon.json

Lines 3822 to 3837 in 9f4f5cd

	"name": "vuestorefront",
	"tags": [
	"framework"
	],
	"versions": {
	"svg": [
	"original",
	"plain"
	],
	"font": [
	"plain"
	]
	},
	"color": "#5ecf7b",
	"aliases": []
	},

In fact, svg type original and plain is not exist 🙌

[amacado]

It's actually not a bug by devicon, but a limitation by our used CDN (jsdelivr.net).
https://cdn.jsdelivr.net/gh/devicons/devicon/icons/vuestorefront/vuestorefront-original.svg

Package size exceeded the configured limit of 50 MB.

Other projects have this problem too, see jsdelivr/jsdelivr#18177

Altough I have no idea why it's reporting this limit when accessing the vuestorefront icon (since it's only a few KB) there's probably not much we can do about. Maybe contacting jsdelivr?

[Thomas-Boi]

Maybe we can fall back to another CDN or using the GitHub link when this happens instead? Here's a response from JSDelivr

Package size exceeded the configured limit of 50 MB. Try https://github.com/devicons/devicon/tree/v2.12.0/icons/vuestorefront/vuestorefront-original.svg instead.

=> we can regexp this to find the url and load the icon that way. It'll be better if JSDelivr can fix this but I think this is a decent fix

[Thomas-Boi]

Just tested the 'fallback' link and it didn't work:
https://github.com/devicons/devicon/tree/v2.12.0/icons/vuestorefront/vuestorefront-original.svg

This link work though:
https://github.com/devicons/devicon/blob/v2.12.0/icons/vueStorefront/vuestorefront-original.svg

I dig around and find this:

Perhaps the error message was wrong? The issue might have been with the folder path name all this time.

EDIT: Yup, it's the path name. This URL works properly (note the vueStorefront rather than vuestorefront) https://cdn.jsdelivr.net/gh/devicons/devicon/icons/vueStorefront/vuestorefront-original.svg

The fix should be done shortly. Perhaps we can make a small patch for this issue?

[Panquesito7]

I think this is fixed now.