Tag
100 articles tagged #JavaScript.
P.01WebTransport hit Baseline in March 2026 when Safari 26.4 shipped it. Here's what it actually does, how it differs from WebSockets, and when to reach for it.
P.02React 19.3 shipped September 9, 2026, and turned two long-experimental APIs stable: View Transitions and Fragment Refs. What changed and whether to upgrade.
P.03ES2026's using and await using close files, connections, and locks when a block ends, with no try/finally. The syntax, real examples, and support today.
P.04Float16Array stores numbers in half the bytes of Float32Array, trading precision most workloads never used. What it's for, what it costs, where it fails.
P.05Chrome 152 added :playing, :paused, :buffering, and :muted as real pseudo-classes. A runnable custom player built on them, plus the JS fallback.
P.06Bun 1.4 is the first stable release on the Rust runtime, adding browser automation, image and markdown APIs, and real speedups. Why it split opinion.
P.07React Router v8 shipped as a deliberately boring release. What the version bump requires, what the codemod handles, and the three things that catch teams.
P.08From Node.js 27 in October 2026, Node drops the odd/even model for one major a year, and every release becomes LTS. What changes, and how to plan for it.
P.09WebMCP is a W3C proposal letting a page register JavaScript functions as tools an agent calls in-browser, no server MCP. How it works, and where it breaks.
P.10Qwik skips hydration instead of optimizing it. How resumability actually works, what Qwik 2.0 changed, and the honest tradeoffs before you ship on it.
P.11Chrome and Edge can prerender the next page before a user clicks, with no SPA rewrite. How the Speculation Rules API works, what it wastes, and shipping it.
P.12No Access-Control-Allow-Origin is the most Googled web error for a reason. What CORS is, why the browser enforces it, and how to configure it properly.
P.13Node.js 24 made type stripping stable and on by default: node file.ts just runs. What that buys you, what syntax it can't handle, and when you compile.
P.14Build browser push yourself with the Push API, Notifications API, and a service worker. No OneSignal, no Firebase. The full setup, VAPID keys included.
P.15Searches for React 20 keep climbing, but the latest release is 19.2.7. What actually shipped in the 19.2 line, including useEffectEvent, and why.
P.16Trusted Types, shape(), and contrast-color() all reached Baseline in early 2026. What each replaces, with working code, and what newly available means.
P.17TypeScript 7.0 hit GA on July 8, three weeks after the RC. The real GA benchmark, what strict mode locks in, and why Astro and Vue projects should wait.
P.18Temporal hit Stage 4 and ships unflagged in Chrome 144, Firefox 139, and Node 26. Migrating common Date patterns to PlainDate, ZonedDateTime, and Duration.
P.19Trusted publishing lets GitHub Actions and GitLab CI publish via short-lived OIDC tokens instead of a stored npm token. The setup, and the May 2026 change.
P.20Node.js 26.5.0 exposed ReadableStreamTee, added streaming Blob text reads and TLS group reporting, plus crypto hardening. What's worth adopting now.
P.21Astro 7.0 rewrote its compiler in Rust, jumped to Vite 8, and switched markdown parsers by default. What changed, what was removed, and how to upgrade.
P.22Bun 1.3 ships Bun.sql for Postgres, MySQL, MariaDB, and SQLite, plus a Redis client it claims is 7.9x faster than ioredis. When switching is worth it.
P.23Attackers used a stolen credential to push five malicious jscrambler versions, each carrying a 7.8MB cross-platform infostealer. What it stole, and how to check.
P.24npm v12 blocks preinstall, install, and postinstall scripts, Git dependencies, and remote tarballs unless allowed. What breaks, and how to migrate.
P.25Full coverage means every line ran, not that your tests would notice it breaking. How mutation testing answers that, with Stryker and mutmut.
P.26TypeScript 7.0's release candidate landed June 18, 2026 with GA about a month out. What's new since beta, real VS Code benchmarks, and a migration checklist.
P.27Vite 8 replaced its dual esbuild and Rollup setup with Rolldown, a Rust bundler, by default. What changed, the real build times, and whether migrating pays.
P.28GitHub's Octoverse 2025 shows TypeScript displacing JavaScript for the first time, driven partly by how AI tools behave with typed code. What the data says.
P.29Astro 6.4 ships a pluggable markdown pipeline and Sätteri, a Rust processor that speeds up content-heavy builds. It can't run your remark plugins yet.
P.30TC39 is standardizing signals, the reactive pattern already inside Vue, Solid, Angular, and Preact. Years from browsers, but it changes what to build on.
P.31TanStack (42 packages) and React Native Aria (17) were hit weeks apart with different entry points and payloads. What each teaches about dependencies.
P.3225,000+ responses, and the picture is consolidation, not churn. Vite at 98% satisfaction, TypeScript exclusive for 40%, React dominant but contested.
P.33TC39 finalised eight proposals for ES2026. Temporal gets the headlines, but Iterator Helpers, Set methods, Promise.try, and RegExp.escape matter too.
P.34Node.js patched 12 CVEs across v22, v24, and v26 on June 18. Two are auth bypasses, and undici's queue poisoning can hand back the wrong response.
P.35Deno 2.9 ships deno desktop, turning any web project into a native app with no Electron boilerplate. What it's for, and when to stay on Tauri instead.
P.36All three frameworks matured and all three make different tradeoffs. The four questions we use with clients, and why there's no universally right answer.
P.37TanStack Start hit 1.x stable and is closing on Next.js in downloads. An honest comparison: what each is good at, where each falls short, how to decide.
P.38React Native's New Architecture is the default now. Screening for JS and native boundaries, Expo tradeoffs, and knowing when cross-platform is wrong.
P.39Firebase's complexity and Supabase's Postgres assumptions don't fit every project. How PocketBase, Appwrite, and Convex differ, and when each one fits.
P.40Frontend developer means different things to different teams. The core screen: HTML semantics, CSS fundamentals, Core Web Vitals, and skill beyond React.
P.41Vue 3 is the default now and the Options API is legacy. What a strong Vue developer looks like, what questions reveal real skill, and the red flags.
P.42TypeScript is the default now, so the market is full of people who write it without understanding it. The questions that tell the two groups apart.
P.43Node.js has split into async-first, TypeScript-native, and edge-runtime camps. The screen that finds someone who builds production backends, not tutorials.
P.44Svelte 5's runes replaced magic variable tracking with explicit reactive primitives. A year into production: what changed, what improved, what surprised.
P.45Three tools, three bets on where complexity belongs. How to choose between BullMQ, Inngest, and Temporal based on what your system needs, not what sounds big.
P.46Playwright dominates scraping now, but tooling is the easy part. A practical guide to scraping that works, and the legal lines to know before you ship.
P.47Expo Router brings file-based routing to React Native, the pattern web developers know from Next.js. Here's how it works and where the friction lives.
P.48While the ecosystem chased Bun, Deno, and edge runtimes, Fastify stayed the production choice for high-throughput Node APIs. Why it still holds up.
P.49SolidJS is not React with a different syntax. It compiles to real DOM operations, skips the virtual DOM entirely, and has a different mental model for reactivity. Here's what that means in practice.
P.50Three.js makes WebGL usable. React Three Fiber makes Three.js feel like React. The fastest path to interactive 3D on the web, and how to use it.
P.51XState v5 ships a rewritten API that's smaller and easier to read than v4. Here's how state machines help in production UI, and what the migration looks like.
P.52Alpine.js adds dropdowns, modals, tabs and form behaviour straight in your HTML, with no build step and no framework. When that's exactly right.
P.53Deno 2 ships with full Node.js compatibility, npm support, and a revised standard library. Here's what that means for teams evaluating it as a serious Node alternative.
P.54TypeScript 5.0 replaced experimentalDecorators with the TC39 Stage 3 proposal: different syntax, more capable, now the standard way to write decorators.
P.55Redux is overkill for most React apps: Zustand and Jotai cover most state needs with far less boilerplate. Here is when to use each and how they actually work.
P.56ESLint 9 made flat config the default and deprecated .eslintrc. Here's what changed, why it's better, and how to migrate without breaking your setup.
P.57Choosing between react-i18next, next-intl, and Lingui comes down to your framework: next-intl for Next.js App Router, react-i18next elsewhere.
P.58Three viable paths to cross-platform mobile in 2026. Which one makes sense depends on your team, your deadlines, and how much of the device you actually need.
P.59Command-line tools are underrated as developer products, and TypeScript makes them maintainable. Parsing, prompts, output, errors, and distribution.
P.60The Date object has been broken for 30 years. Temporal is its replacement, now shipping in browsers and Node.js. Here's what actually changed and how to use it.
P.61NestJS is Express with structure imposed: modules, dependency injection, decorators. When that pays for its learning curve, and when it does not.
P.62AI tools write code fast. TDD asks you to slow down and write tests first. These two impulses seem to be in tension. Here's how they actually work together.
P.63WebGPU is now in Chrome, Firefox, and Safari: a general-purpose GPU compute layer, not just graphics, for ML inference, image processing, and simulation.
P.64Structured commit messages unlock automatic changelogs, version bumps, and release notes. The full setup, from commitlint hooks to shipping in CI.
P.65Three different approaches to styling a web application — Tailwind, CSS Modules, and CSS-in-JS libraries — and the team contexts where each one actually makes sense.
P.66Manifest V3 changed how Chrome extensions work. Here's what actually matters for developers building extensions today: service workers, declarativeNetRequest, and the gotchas nobody warns you about.
P.67Local-first means your app works offline and syncs when connected. The technology (CRDTs and sync engines) is mature enough to use. The question is whether your use case actually needs it.
P.68Three animation options dominate web development right now: CSS, Framer Motion, and GSAP. Here's how to pick the right one for your project and why the native platform is better than you might expect.
P.69The View Transitions API and scroll-driven animations are now baseline in every major browser. Here's what they replace and working code for both.
P.70The command line tools most developers use today are a decade old. Here's what's replaced them and why: terminals, Git UIs, shell configuration, and the small tools that compound into significant time savings.
P.71A Playwright E2E suite that scales reuses auth state across tests, follows a folder structure built for growth, and configures CI to isolate real flakiness.
P.72React Native's new architecture shipped as stable and has been default since RN 0.76. Here's what the Fabric renderer and JSI bridge replacement changed, what the migration looks like in practice, and where the remaining rough edges are.
P.73Media queries ask 'how wide is the viewport?' Container queries ask 'how wide is my parent?' That shift changes how you think about reusable components.
P.74If your design system needs to work in React, Vue, and a legacy jQuery app simultaneously, Web Components are the only native answer. Lit makes them practical to write.
P.75Google's crawler runs JavaScript, but on a delay and with different limits than a browser. Here's where JS app SEO actually breaks, and how to test for it.
P.76PWAs got a second wind once iOS 16.4 enabled push notifications and iOS 17 improved install flow. The gap between PWA and native is now narrow enough to matter.
P.77The Vercel AI SDK has become the default for building AI features in JavaScript apps. Here is what it actually does, how its core primitives work, and where the sharp edges still live.
P.78TypeScript leaves errors untyped by default. Effect TS fixes that with typed failures, dependency injection, and structured concurrency.
P.79Vuex was Vue's state library for years, and Pinia replaced it as the official recommendation. How Pinia works, and where it fits in a Vue 3 app.
P.80Hono started as a tiny router for Cloudflare Workers and became the default for edge APIs. What it does well, and why "runs everywhere" actually holds.
P.81Interaction to Next Paint replaced First Input Delay in 2024, and most sites still haven't caught up. INP is harder to optimize because it measures every interaction, not just the first one.
P.82Tauri 2.0 added iOS and Android while keeping tiny binaries, a Rust backend, and the OS webview instead of a bundled Chromium. How it works, and when.
P.83Drizzle is the TypeScript-first alternative to Prisma: schema in TS, migrations in SQL, no query engine binary. How it works, and when to pick it.
P.84Vitest runs faster than Jest, handles ESM and TypeScript natively, and shares Jest's API. The case for switching in a Vite project, and how to do it.
P.85Biome is a Rust-based toolchain that replaces ESLint and Prettier with one fast binary for linting, formatting, and imports. Here is what migrating looks like.
P.86Not every real-time feature needs WebSockets. Server-Sent Events handle most push scenarios with far less complexity. Here's how to choose, and what each approach looks like in actual code.
P.87Playwright E2E tests break because of fragile selectors, shared test state, or overly broad scope, not the tool itself. Fix those and tests survive UI changes.
P.88Video calls, live collaboration, real-time audio — features clients want more than ever. WebRTC makes them possible, but the gap between a working demo and a production deployment is wider than the documentation suggests. Here's what that gap looks like.
P.89EditorPickBun hits 52K req/sec, Deno 2 achieves full npm compatibility, and Node.js remains the enterprise standard. A practical comparison with benchmarks, code examples, and migration guides.
P.90EditorPickWe have built production apps with all three. Here is an honest comparison of Next.js 15, Astro 5, and Remix covering performance, DX, and when to use each.
P.91Our curated list of npm packages that make it into every CODERCOPS project. Each one battle-tested across 30+ production apps with alternatives we considered.
P.92Vue 3.6's Vapor Mode compiles templates straight to DOM operations, skipping the virtual DOM entirely. We break down the benchmarks and the real tradeoffs.
P.93Anders Hejlsberg announced the Go-based TypeScript compiler in March 2025. With TypeScript 7.0 on track for mid-2026, early benchmarks show 10x faster type-checking. We unpack what this means for your projects.
P.94Vite started as a dev server experiment by Evan You. In 2026, it is the default build tool for nearly every major framework. We trace how it won, what the modern JS toolchain looks like, and where Webpack fits now.
P.95Remix 3 drops React for a Preact fork and web-standards-first architecture. Here's why this matters, what it means for React developers, and whether the post-React era is truly upon us.
P.96jQuery 4.0 shipped January 17, 2026, its first major version in a decade, and it still runs 77% of JS-powered websites. Here's what's new and who should upgrade.
P.97A CVSS 10.0 pre-auth RCE in React Server Components was exploited within two days of disclosure. Here's the patch guidance and what changed.
P.98EditorPickFrom AI-first development to meta-frameworks dominance, discover the key trends shaping web development in 2026 and how to stay ahead of the curve.
P.99EditorPickReact 19 shipped Server Components, Actions, a built-in compiler, and new hooks like useOptimistic and use(). Here's what changed and how to migrate.
P.100TypeScript 5.8 brings improved type checking, direct Node.js execution, and better JavaScript interoperability. Here's everything developers need to know.