Document the official MIME type for `.vue` files

[MichaelDeBoey]

I’m working on improving MIME type support for modern web framework source files across tooling, servers, and content-type databases.

Currently, there does not appear to be an officially documented MIME type for .vue files.
Some tools/frameworks use conventions such as text/x-<framework>, but there is no authoritative reference from the Vue project itself.
This create ambiguity for other projects to rely on a consistent mapping.

Having an official statement would help:

• MIME databases include the mapping
• web servers and CDNs configure correct content types
• editors and language servers align
• reduce ecosystem fragmentation

Would the Vue project be open to document an official recommendation for the MIME type of .vue files?

This does not necessarily require IANA registration though.
A short note in the docs would already provide a reliable reference for downstream projects I think.

If another MIME type from text/x-vue (like text/plain, text/html, text/html+vue, ...) is preferred, documenting that choice would be equally helpful.

Thank you for your work and for considering this!

CC/ @yyx990803

[jonchurch]

As the mime-db maintainer who suggested reaching out to Vue for this, I want to make sure I’m giving you good guidance here.

Can you describe a concrete scenario where a user or system needs to serve a raw .vue file over HTTP with a correct Content-Type header? I’m thinking about the actual .vue SFC, not compiled output.

I ask because I’m trying to understand the bigger picture you outlined in your description here.

These file types (astro, vue, ts, svelte) usually never leave someone's build pipeline. They have generally gone without formal MIME types and I’m not aware of downstream projects that have been blocked by that. Is there a specific project or workflow that motivated this?