Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider using a cross-platform extension framework for easier development and maintenance #2

Open
SethBurkart123 opened this issue Jun 20, 2024 · 0 comments

Comments

@SethBurkart123
Copy link

Hey there! 👋
I've been following the progress of open-webui and finally this extension, and I must say, I'm really excited about what you've accomplished so far. I develop chrome extensions for fun, and I know firsthand the challenges that come with making an extension work seamlessly across different platforms.

I wanted to reach out because I've been thinking about ways to make the development process smoother and more efficient. One idea that came to mind is using a cross-platform extension framework. These frameworks handle the heavy lifting of generating browser-specific packages and provide handy polyfills, making it a breeze to target different browsers without all the manual work.


I've had some great experiences with two frameworks in particular:

  1. Bedframe: Built on top of https://github.com/crxjs/chrome-extension-tools
  • Simplifies targeting different browsers
  • Implemented as a Vite plugin, which could be useful if you need any niche Vite plugins or just prefer Vite altogether
  1. Plasmo: Built on https://parceljs.org/ (known for its speed and performance)
  • Extensive support for a wide range of plugins
  • Can handle pretty much any requirement you throw at it

I've personally converted a few large-scale extensions to use these frameworks, and the results have been fantastic. It significantly reduces the development effort and ensures a consistent user experience across platforms.
If you're open to the idea, I'd be more than happy to lend a hand in integrating either Bedframe or Plasmo into the project. I think it could be a game-changer for the development workflow and make maintaining the extension a whole lot easier in the long run.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant