for context, if an invalid file is identified, this error is returned:

No supported file type
Error: No supported file type at EV.readFileType (https://coder.internal.dev/assets/editor.main-8670c423.js:1:3159) at EV.readFileInfo (https://coder.internal.dev/assets/editor.main-8670c423.js:1:2353) at EV.readFile (https://coder.internal.dev/assets/editor.main-8670c423.js:1:2194) at async lbe (https://coder.internal.dev/assets/editor.main-8670c423.js:1:6074) at async Promise.all (index 1) at async loadFiles (https://coder.internal.dev/assets/TemplateVersionPage-e5fb6a46.js:1:1876)

this also causes the Source Code page to hang and Edit page return as blank for the template in question.

What additional types are you trying to support?

@Emyrk we don't have a specific set of files we want to support. Handling tar files in a specific way can be painful since we usually don't have access to the customer .tar template to verify them and it can take long to get it, debug and get a fix. Also, understanding each of the file types in tar deeply sounds too much for now. IMO, we should not block or handle a specific set o file types until we have a good reason for that. We made this before because the code that I took as base had it and I didn't see a reason to remove this part.

Merging it for now. If you see any issue with that we can easily revert.