BellCube

BellCube

@bellcube.dev

Complete nerd, always interested in learning cool new things! 🐙 https://github.com/BellCubeDev/ 💼 Full-stack nerd for hire! https://bellcube.dev/

8 followers22 following31 posts

BellCube reposted

❓"When can we expect this feature" Please refrain from asking this question towards open source maintainers. You generally shouldn't "expect" anything. I don't often agree with DHH but his take on OSS being a gift, not something you're entitled to, is something I relate with.

I've gotten oddly good results by downloading an entire library/framework's docs MD collection, putting it in a folder, asking AI agents to make sure everything's set up and up to snuff, and repeat the prompt about 20 times. You can do multiple libraries at a time, too! Works well for project setup.

BellCube reposted

Did you know your MacBook has a sensor that knows the exact angle of the screen hinge? It’s not exposed as a public API, but I figured out a way to read it and make it sound like an old wooden door.

BellCube reposted

A number of popular npm packages have been compromised and malicious versions published. Most of these have been removed from the registry. Astro indirectly depends on one that hasn't, so we have published 5.13.6 that pins a safe version.

socket.devnpm Author Qix Compromised via Phishing Email in Major Suppl...npm author Qix’s account was compromised, with malicious versions of popular packages like chalk-template, color-convert, and strip-ansi published.

ok so I checked the #FrontendDev tag after my last post and I don't think I've ever gotten self-promotion and grifter whiplash harder in my life.

OK so this thing is neat. Will almost certainly become a mainstay of my #FrontendDev workflow. Genuinely makes it easy to see how #responsive designs, well, respond to different screens in one go. And easy to remember to check different screen sizes (hobbyist problems). bsky.app/profile/gith...

GitHub Trending JS/TS@github-trending-js.bsky.social

🔥 Hot Repo! 🔥 (100+ new stars) 📦 responsively-org / responsively-app ⭐ 23,772 (+143) 🗒 JavaScript A modified web browser that helps in responsive web development. A web developer's must have dev-tool.

BellCube reposted

I love CSS folks. They are soldiers of joy and delight. The world is burning and AI debates have people at each others throats and CSS peeps keep being like “check out this dancing turtle I made out of divs 🥰”

BellCube reposted

As a way of combatting my perfectionist tendencies I created a “sketches” section on my blog as a place to put prototypes and “here’s how I solved this problem” type posts without wanting to polish them forever We’ll see if that helps 🤞

My philosophy when it comes to #developer-tooling is to add as many layers of #idiot-proofing as possible. I say this because I know I'm an idiot. Though, of course, practical gripes can get in the way quite easily. I don't think I would've used #React 5 years ago because the ecosystem sucked.

That's why I use web frameworks like #React; that's why I use #ORMs like #Prisma and #Drizzle; that's why I use #TypeScript; that's why I love #linting; that's why I use #CoderRbbit on solo projects; that's why #linaria #css-in-js caught my eye.

BellCube reposted

Replying to @jaredwhite.indieweb.social.ap.brid.gy

I don't even know how a bug like that makes it past typecheck, lint, and code review— It's magical that, in the Year of Our Lord 2025, we still have null value bugs. AI-induced or not, this is impressive.

I feel like using NPM package search is a web developer hazing ritual that nobody every talks about. Now, I don't have any ideas in my head to make it better, but it is far too difficult to find up-to-date, worth-using packages for what you want.

Semi-regular reminder that #passkeys are probably the greatest thing to ever hit the #authentication scene since password hashing #cryptography. Convenient for users, impossible to #phish, and simple enough you can safely roll passkey support yourself. Only caveat is transferability... #webdev #auth

Now, of course, #passkeys not being transferable is a mainstay, so how do we solve this problem? My solution when I was looking at it was to use one passkey to authenticate another one. New devices would create a "Passkey Request" (behind a CAPTCHA) and an existing device would approve the request.

You are up to date.