plasmo

As I mentioned, it is a research project, so I would not expect production ready code or multi-browser support. They are indeed not supporting the old version, as they are rewriting almost everything from scratch. Last time I had contact with them, they were exploring using Plasmo [1] as building block for the extension, instead of doing everything vanilla as they did in the 1st version, which would offer cross-browser support out of the box. But meanwhile, you can check the code [2] and add the FF manifest yourself to try it out. [1] https://github.com/PlasmoHQ/plasmo [2] https://github.com/Vis4Sense/HistoryMap

Sorry I'm dumb: https://github.com/PlasmoHQ/plasmo

https://github.com/PlasmoHQ/plasmo/discussions/803 From my personal experience; most stuff just works cross platform. Currently building an extension and it just works in edge, chrome, Firefox, safari. You can use poly fill or custom code for when it’s really needed of course

There's also Plasmo which provides some abstractions over the browsers: https://github.com/PlasmoHQ/plasmo

Ooof!! It is an... interesting time right now in extensions land. The switch from MV2 to MV3 is a bit chaotic but hopefully tools like this (Bedframe) and tools like [Plasmo](https://github.com/PlasmoHQ/plasmo) start to inject some freshness in the space.

Shameless plug, but we built the Plasmo Framework to make that (and a lot more) super easy: https://github.com/plasmohq/plasmo

Thanks! We wrote a custom Parcel runtime [1] inspired by Parcel's HMR runtime (which was too bloated and buggy for us) that injects a web socket listener into the development build of the extension. Whenever a bundle change happens, Parcel sends it the refresh message and it either does `chrome.runtime.reload()` or `location.reload()` depending on the context. [1]: https://github.com/PlasmoHQ/plasmo/blob/main/packages/parcel...

Hey HN, we're excited to have people try out our framework! When we built out a Chrome extension earlier this year, we noticed that the config was too imperative. You had to constantly tell Chrome via the manifest.json file where your files were, what your permissions should be, etc. So we thought it might be interesting to build a more declarative framework. When we built a proof of concept, we enjoyed working with it and decided to invest more time into making it usable and adding more features. We're still pretty early in building it out, and there's a bunch more we want to add, but this feels like a good time to showcase it and hear what people think!

404: https://github.com/PlasmoHQ/plasmo