Topic
30 articles found
Originally published on the Cosmic blog. Bun v1.3 is the fastest JavaScript runtime you can use right now. Cosmic's REST API returns content in under 100ms. Put them together and you get a full-stack setup that's faster at every layer: cold starts, package installation, HTTP requests, and content de
Angular's @switch block has become a lot more useful recently. With exhaustive type checking, Angular can now catch missing template states when a TypeScript union or enum changes. And with grouped cases, we can remove duplicate markup when multiple states render the same UI. In this post, I'll show
▶️ Play it first (10 seconds): https://emaadshamsi.github.io/paper-hands/ It's called PAPER HANDS. One button. The line goes up while you hold — your rugs. Let go to bank it. Hold too No engine, no build step, no dependencies — one index.html, ~250 lines of Canvas. The mechanic is a single tension:
Mastering CSS Grid Subgrid: A Complete Guide Grab your coffee, pull up a chair, and let's talk about one of the most satisfying CSS features to finally hit prime-time browser support: CSS Grid Subgrid. You know the exact headache I’m talking about. You’re building a classic card layout. Each card ha
I have been working on a project called SEOCore, which is an SEO crawler and audit CLI built with TypeScript. It is also my first public repository, so this project means a lot to me. Building it has been a mix of learning in public, solving real problems, making mistakes, and slowly improving thing
It feels like we spent the last decade making web development intentionally difficult. But if you are working in the .NET ecosystem, Blazor offers a massive escape hatch. It moves past the bloated state-management traps of modern JavaScript, allowing you to write clean, component-driven, type-safe U
Most websites work. They load. But many of them still feel static, generic, and forgettable. I wanted to explore how motion, pacing, and scroll progression can make a website feel more like an experience instead of just a page. So I built a cinematic scroll-controlled demo using: HTML CSS JavaScript
It's midnight. You get an incident call on your phone that your application's web server has crashed, and users are seeing the dreaded 500 Internal server error. You stumble to your laptop, sleepy-eyes, to run the restart command or to run your restart script. This is the "Old Way." It's manual, it'
Every web developer knows TinyPNG. It's been the go-to image compressor for years. But after years of using it, I started questioning: why am I uploading my images to someone else's server? Tools like TinyPNG, Compressor.io, and even Squoosh (partially) require you to upload images to their servers.
I have refreshed my page multiple time but hit with this same problem what shall i do? 1 post - 1 participant Read full topic
Every web developer hits URL encoding bugs eventually. A redirect loop that only happens with certain usernames. A search feature that breaks when someone types C++. An API that returns garbage when the query contains emoji. These bugs are annoying because they fail silently — the URL looks fine in
We spent years getting TypeScript to where it is. It already checks your APIs, your components, your state. Your CSS values are still strings that nothing compiles. Why wait for a new tool when the one you have can do this today? A 2025 academic study [1] found that 94% of LLM-generated compilation
The landscape of data fetching in React has more options than ever. Here is when each one is the right choice: Scenario Approach Server Component fetching data async / await directly in the component Passing async data from Server to Client Component Create promise on server, use() on client with Su
The CI was green. Build passed. No TypeScript errors. No warnings. Everything looked clean. I clicked deploy and went to make tea. Came back, opened staging, and things were broken in ways that made no sense. A redirect wasn't working. Lint had silently disappeared from the build pipeline. One API r
Hey everyone! I am Pahal Desai, a 16 year old student who is trying to create my own open-source Chromium-based web browser called Neovex. I am a beginner in C++, and to be honest, a few weeks ago I had almost no idea how browser development actually worked. So why am I building a browser when there
A few months back I contributed a fix to react-bits, an open source library of animated React components. The bug was subtle — enableMagnetism and enableTilt animations had a 300ms delay because the component used transition-all in its base CSS class. This caused GSAP transform animations to fight a
I've always wondered how to handle those single-record things in a CMS-driven site. You know what I mean — the home page hero, the blog page header, the pricing section banner. They're not a list. There's no "add another." There's exactly one of them, and a non-technical client or even your future s
useState looks simple on the surface, but behind it is one of the core ideas that makes React work: persistent state + re-rendering. In this article, we'll build a tiny version of useState ourselves to understand the mental model behind it. First, we know that the useState returns a state and a func
Originally published on subhanfarrakh.com/blog Most portfolio sites don't need React to render a headline. Yet most developers — myself included — reach for a React SPA by default. The result is hundreds of kilobytes of JavaScript shipped to the browser before a single word of content appears. I spe
framework-http-request-headers.md Comprehensive reference for the eleven HTTP request headers most relevant to server side decisions about how to respond, route, log, throttle, or filter: User-Agent (identity, never to be trusted alone), Accept (content type negotiation), Accept-Language (language n
