Post

I posted this yesterday but I walked back the decision for the expensive premium domain, and tsv is now grouped with my other projects at fuz.dev -- I deleted the post because I don't want it pointing to a domain that might get malware next year

I'll be announcing more of the Fuz projects soon. fuz_css and fuz_ui are probably most relevant to people interested in tsv -- feedback is welcome, unlike tsv they're not AI generated, I built them over 7 years and I think I'm near the point where they won't have continuous breaking changes

This first release took 7 months and ~1800 manual commits. Fixtures are all original - I used Prettier's only after it formatted my codebases and Svelte's, and avoided many bugs and quirks in the process. I used machine agents but I put considerable effort into the design choices and quality.

how do you think this compares to something like @biomejs.dev?

No formatting options? Eg semi: false, singleQuote: true, tabWidth: 4, printWidth: 100, quoteProps: 'as-needed', bracketSpacing: false, arrowParens: 'avoid',

Impressive. Where does this fit relative to oxc and rsvelte?

rsvelte uses oxc, tsv has its own parser today tsv is ~6% slower formatting TS and oxfmt bundles+delegates to Prettier, so tsv's wasm is 9x faster formatting Svelte & 13x for CSS, natively 12x/17x oxlint bridges to JS for ESLint plugins, and oxfmt is planning Prettier plugins - tsv won't for perf

tsv is focused on Svelte+TS+CSS (can output Svelte's AST), oxc is a Biome-like generic language platform tsv won't support config options so filesystem state doesn't affect how it operates rsvelte started with a Svelte compiler, tsv's is deferred for now size-wise this means tsv is much smaller