JoeyDoey
Joined 16 years ago
Karma
122
Submissions
52
Member since
Jun 24
building monoliths @ https://specialize.studio |
making beds @ https://bedframe.dev
View on Hacker NewsRecent submissions
Comment · 10 months ago
Wanted to design a nice lil macOS icon but ended up building an app to go along with it. Building a macOS AI image studio app https://picchat.ai/
Comment · 2 years ago
Looks like Codemirror does similar with long/ huge files https://codemirror.net/examples/million/
Comment · 3 years ago
https://github.com/nyaggah/bedframe/
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!
Comment · 3 years ago
thanks, bruv!
Comment · 3 years ago
Bedframe gives you that, basically. It's a project generator that uses Vite so it'll let you build in vanilla js and html/css and enables dev niceties like HMR so you have a live dev server, etc. but in the end you end up with just the html/css/js.
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.
Comment · 3 years ago
Plasmo? They're certainly further along in dev and doing great work.
Bedframe is a slightly differing approach to the same pretty much.
Comment · 3 years ago
Yes to all this. But the project is super new so supports just React right now.
The idea is to support all officially supported vite templates in ts and js, so:
vue, react, preact, lit, svelte, solid, qwik.
> 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.
Comment · 3 years ago
VS Code is "Community Material Theme" - hight contrast:
https://marketplace.visualstudio.com/items?itemName=Equinuso...
Comment · 3 years ago
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.
Comment · 3 years ago
Author here! the project is super new. alpha, at best.
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