JoeyDoey

A cross-browser extension development framework. Got some good feedback on it on here earlier (https://news.ycombinator.com/item?id=37394194) and still hacking away at it. Appreciate any feedback!

Great projects on here so far!

Idea is, depending on what kind of extension you're building you can use content scripts to render you extension in shadow dom or iframe. Bedframe lets you do this.

The CLI is a project generator for: - popup (default kind of extension) - side panel (relatively new in Chrome / https://developer.chrome.com/docs/extensions/reference/sideP...) - overlay (what you describe above) - devtools extensions (https://developer.chrome.com/docs/extensions/mv3/devtools/#d...).

Bedframe goes further and lets you add a mvp.yml workflow to your (Github) repo and have any versioned changes landing in 'main' branch get published to firefox, edge, chrome web stores

Basically productionizes the extension dev process.

> what its trying to solve:

I want a Next.js + Vercel dev experience but for building browser extensions: push to main > run a workflow > determine if it should publish > publish (to all my chosen web stores)

I want an actual dev workflow (like I'm used to in regular web/app development in 2023) but again, tailored for browser extensions.

Basically I wanted something that doesn't abstract the usual Vite setup. Just give me the usual niceties of working with client-side react w/ Vite. So yes, you get the vite/rollup plugins as usual.

Basically if you wanted to build browser extensions using modern stack, bedframe lets you do that. Specifically it uses Vite under the hood so you can write e.g. a chrome extension in e.g. React w/ TypeScript, Tailwind, and all that good stuff.

I think the CLI readme has a bit more useful info: https://github.com/nyaggah/bedframe/tree/main/packages/cli

The notable bit is the mvp.yml workflow you get in your project. It'll let you publish to chrome, firefox and edge automatically (ci/cd).

> It's also very unclear what state this project is in.

fair enough! Wanted to get something out there first; I'll get the docs out soon

- Great point. I'll change that.

- That was the idea. That you'll keep using the service.

- Right now I take whatever material is submitted to me and I design the ebook and output it in the different formats. I'm not distributing it (to itunes, Amazon, etc) quite yet. Down the road perhaps.

Re: logo, the E and the B just lent themselves nicely to arbitrary ligature. It does make it slightly hard to read I admit.