// the find
TheLarkInn/unity-component-specification
This is a WIP draft of the Unity (Single File Web Component) Specification
A 2017 draft spec for a framework-agnostic single-file component format, intended to let the same `.sfc` file work in Vue, React, Preact, and eventually as native browser instructions. Written by Sean Larkin (webpack team) as a thought experiment after working on webpack's module system. It never left draft status.
The problem statement is real — cross-framework component portability is a genuine pain that Web Components have never fully solved. The Vue SFC analogy as a 'likeness not literal HTML' is a useful conceptual frame. The cons section is surprisingly honest for a spec draft, acknowledging silver-bullet syndrome and framework capability dilution upfront.
Nothing was ever built — no parser, no compiler, no reference implementation, no tooling. Abandoned in August 2017 with 219 stars and zero follow-through; the TODO comments outnumber the actual spec. The core mechanism (browser compiling `.sfc` to 'native instructions') is never defined beyond wishful thinking — it assumes browser vendors would implement something that has no W3C process, no champions, and no prototype. Module Federation, Astro's component islands, and framework-native solutions have made the cross-framework interop problem much less pressing since then.