Instead of bundling the list of supported file type icons, I believe it would be more convenient to modify the list of supported icons from a remote place, have the plugin fetch the mapping as a JSON file from some static URL, cache that locally, and base icon name resolution on that. With this, it wouldn't be required to package a new release simply for an added icon.
A suitable location would be a JSON file in the default branch, where it would double-serve as an automatically semi-up-to-date fallback for packaged releases (readable via sublime.load_resource).
Instead of bundling the list of supported file type icons, I believe it would be more convenient to modify the list of supported icons from a remote place, have the plugin fetch the mapping as a JSON file from some static URL, cache that locally, and base icon name resolution on that. With this, it wouldn't be required to package a new release simply for an added icon.
A suitable location would be a JSON file in the default branch, where it would double-serve as an automatically semi-up-to-date fallback for packaged releases (readable via
sublime.load_resource).