docs VS sveltekit-adapter-browser-extension

Plasmo: A framework for building Chrome extensions.

Check out https://docs.plasmo.com/

- We have remote code bundling that automatically fetches URL based imports (like Google Analytics) in build time to mitigate issues with MV3 not allowing remote code [4]

[1]: https://docs.plasmo.com/#where-is-the-manifestjson-file

[2]: https://docs.plasmo.com/workflows/env

[3]: https://github.com/PlasmoHQ/examples/tree/57791e70549441e391...

[4]: https://docs.plasmo.com/workflows/remote-code

We decided to tackle this problem by building a framework for browser extension development called Plasmo. It's a different way of thinking about browser extensions, and if you're used to building extensions, some things might look a bit weird.

Would love to get people to try it out and get feedback. Right now, we're focusing only on supporting React so that we can iron out all of the different edge cases that might arise, but will look to add other view frameworks like Svelte, Vue, etc. in the future! Here are the docs: https://docs.plasmo.com

Fixed - it should point to the https://github.com/PlasmoHQ/docs instead

Sveltekit! I used sveltekit-adapter-browser-extension[0] by Antony which conveniently handles the hashing stuff. I just made the repo public in case you want to check it out[1]. Let me know if you run into any issues!

[0] https://github.com/antony/sveltekit-adapter-browser-extensio...

[1] https://github.com/FractalHQ/nutab

Sveltekit is meant to be used with potentially any deployment method. I haven't tried it but there is a browser-extension adapter (unofficial but made by core team members), might be worth a try.