Comparison Documentation

[Malix-Labs]

Hello folks

It would be very nice to have a comparison documentation with the competition (such as plasmo), and also state why not using bundler plugins (such as CRXJS)

It would also be nice to note there your motivation as of why you started developing WXT rather than using the already developed plasmo
And state what do WXT solve better (and maybe also solve worse for now)

I think it would also make more people consider tradeoffs between both, and ultimately make them switch to better tech

References

• star history

[aklinker1]

This already exists:
https://wxt.dev/guide/compare.html

I could add comparisons to bundler plugins as well.

[aklinker1]

I've updated the comparsion page. Let me know if there's any comparisons you think are important that I'm missing.

[Malix-Labs]

Saw the update
It's a nice addition and interesting to read!

Are there any technical difference that made you prefer to start WXT from scratch instead of starting with a fork of Plasmo (and perhaps even contributing to upstream)?

[aklinker1]

Vite has emerged as the top bundler the last few years, so rather than forking and working with parcel, I chose to start from scratch with Vite.

[Malix-Labs]

Very understandable then.
Thanks!

[sir-kokabi]

This already exists: https://wxt.dev/guide/compare.html

I could add comparisons to bundler plugins as well.

New compare link:
https://wxt.dev/get-started/compare.html

[ultrox]

For anyone looking there is a new page:

https://wxt.dev/guide/resources/compare.html

BTW what I really like about WTX is smaller dependency surface. I work in enterprise env and a lot of things are blocked. Plasmo could not be installed because of sharp (which I was able to override) and node-gyp which finally made me quit.

Wtx went smooth as butter. Thanks for your work

[Malix-Labs]

WXT is definitely the current best way dev tool to build browser extension

Also see my thread and answer about that :
crxjs/chrome-extension-tools#872 (reply in thread)