How does this compare to WXT[0]? I recently built a new tab extension[1] which uses quite a few permissions and browser APIs and building for Chrome and Firefox was a non-thought with how seamless compilation and distribution was.
It even separates the built extension code and the source and packages it nicely for firefox's review process.
There is a faq entry about that on tfa. The main differences are use of rsbuild (not a big diff down the line I expect, since vite uses rolldown now), and design to accommodate llm agentic development.
How does this compare to WXT[0]? I recently built a new tab extension[1] which uses quite a few permissions and browser APIs and building for Chrome and Firefox was a non-thought with how seamless compilation and distribution was.
It even separates the built extension code and the source and packages it nicely for firefox's review process.
[0] https://wxt.dev [1] https://chromewebstore.google.com/detail/commander/pgfpnakgi...
There is a faq entry about that on tfa. The main differences are use of rsbuild (not a big diff down the line I expect, since vite uses rolldown now), and design to accommodate llm agentic development.
I did read that LLM generated paragraph but I was thinking there was some architectural difference/some improvement to existing tooling.
I don't mean to sound too dismissive but just slapping on rsbuild and well formatted errors + llms.txt doesn't seem that useful?
Wow a bunch of generated text that tells me everything is covered. Also using the same style as FF, along with suffixing kt with fox.
I sure wonder where you got the inspiration from! (If there was any).