Tag
80 articles tagged #JavaScript.
P.01Astro 7.0 shipped a full Rust rewrite of its compiler, a jump to Vite 8, and a default markdown parser switch, plus a short list of breaking changes. Here's what changed, what got removed, and a practical checklist for upgrading a real project.
P.02Bun 1.3 ships Bun.sql, a unified client for Postgres, MySQL, MariaDB, and SQLite, plus a native Redis client Bun claims is 7.9x faster than ioredis. Here's the real API, working code, and when it's actually worth dropping your existing driver.
P.03On July 11, 2026, attackers used a stolen publishing credential to push five malicious versions of the jscrambler npm package, each carrying a 7.8MB cross-platform infostealer. Here's what it stole and how to check if you're affected.
P.04npm v12, shipped July 8, 2026, blocks preinstall/install/postinstall scripts, Git dependencies, and remote tarball installs unless you explicitly allow them. Here's what breaks, why it's happening now, and the exact commands to migrate a real project.
P.05100% code coverage tells you every line ran during your tests. It says nothing about whether your tests would notice if that line broke. Mutation testing answers that question directly, here's how to run it with Stryker and mutmut and what to do with the score.
P.06TypeScript 7.0's release candidate landed June 18, 2026, with GA expected within about a month. Here's what's new since the beta, the real VS Code benchmark numbers, and a concrete migration checklist.
P.07Vite 8 replaced its dual esbuild/Rollup setup with Rolldown, a Rust-based bundler, as the default. Here's what actually changed, the real build-time numbers, and how to tell if migrating pays off for your project.
P.08GitHub's Octoverse 2025 report shows TypeScript displacing JavaScript as the most-used language on the platform for the first time, driven partly by how AI coding tools behave differently with typed versus untyped code. Here's what the data actually shows.
P.09Astro 6.4 ships a pluggable markdown pipeline and Sätteri, a Rust-based processor that measurably speeds up builds on content-heavy sites. It also can't run your remark or rehype plugins yet. Here's when the trade is worth it.
P.10TC39 is standardizing signals as a native JavaScript primitive, the same reactive pattern already inside Vue, Solid, Angular, and Preact. It won't ship in browsers for years, but it changes what's worth building a library around today.
P.11In May and June 2026, two separate supply chain attacks hit the npm ecosystem — TanStack (42 packages) and React Native Aria (17 packages). They used different entry points, had different payloads, and should change how every team handles third-party dependencies.
P.12The State of JavaScript 2025 survey results landed in March 2026. 25,000+ responses, and the picture it draws is less 'everything is changing' and more 'the things that work are consolidating.' Vite at 98% satisfaction. TypeScript exclusive for 40% of developers. React dominant but contested.
P.13TC39 finalized ECMAScript 2026 with eight proposals at the March 2026 plenary. Temporal gets the headlines, but the rest of the spec (Iterator Helpers, new Set methods, Promise.try, RegExp.escape, and Float16Array) is worth understanding too. Here's what ships and when you can use it.
P.14Node.js pushed security updates on June 18, 2026 across v22, v24, and v26, patching 12 CVEs. Two are high-severity auth bypasses. The most interesting is undici's HTTP response queue poisoning, which can send the wrong response to the wrong request on keep-alive connections.
P.15Deno 2.9 ships deno desktop — a way to turn any web project into a native, distributable desktop app with no Electron boilerplate. Here's what it does, what it's good for, and when to keep using Tauri or Electron instead.
P.16The three major frontend frameworks have all matured significantly and all make different tradeoffs. This is how we help clients choose — and why there is no universally right answer.
P.17TanStack Start hit 1.x stable and is now closing in on Next.js in weekly downloads. Here's an honest comparison of both frameworks — what each is good at, where each falls short, and how to make the call for your project.
P.18React Native's New Architecture is now the default. Hiring a good RN developer means finding someone who understands JS/native boundaries, Expo's trade-offs, and when cross-platform is the wrong call.
P.19Firebase's complexity and Supabase's Postgres assumptions do not fit every project. PocketBase, Appwrite, and Convex each solve the backend problem differently. Here is when each one makes sense.
P.20Frontend developer means different things to different teams. This guide covers the core screen: HTML semantics, CSS fundamentals, Core Web Vitals, and how to test for real skill rather than framework familiarity.
P.21Vue 3 is now the default and the Options API is legacy. This is what a strong Vue developer looks like in 2026, what questions reveal real skill, and what red flags to watch for.
P.22TypeScript is now the default for most web projects, which means the market is full of developers who write TypeScript without understanding it. Here is how to tell them apart.
P.23Node.js has fractured into async-first, TypeScript-native, and edge-runtime camps. This is the practical screening guide for hiring a Node.js developer who can build production backends, not just Express tutorials.
P.24Svelte 5's runes replace the old magic variable tracking with explicit reactive primitives. A year into production use, here is what changed, what improved, and what surprised us.
P.25Three tools, three different bets on where complexity belongs. Here's how to choose between BullMQ, Inngest, and Temporal based on what your system actually needs — not what sounds most impressive.
P.26Playwright has become the dominant web scraping tool, but the tooling decision is the easy part. Here's a practical guide to scraping that works, and the legal and ethical lines you need to know before shipping.
P.27Expo Router brings file-based routing to React Native, the same pattern web developers know from Next.js. Here's how it works, what it gets right, and where the friction still lives.
P.28While the JavaScript ecosystem chased Bun, Deno, and edge runtimes, Fastify quietly became the production choice for high-throughput Node.js APIs. Here's why it's still the right call for many teams.
P.29SolidJS 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.30Three.js makes WebGL accessible. React Three Fiber makes Three.js feel like React. Together they're the fastest path to interactive 3D on the web. Here's how to actually use them.
P.31XState v5 ships a rewritten API that's smaller, faster, and easier to read than v4. Here's how state machines actually help in production UI, and what the migration looks like.
P.32Alpine.js lets you add dropdown menus, modals, tabs, and form behavior directly in HTML without a build step or a JavaScript framework. Here's when that's exactly what you want.
P.33Deno 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.34TypeScript 5.0 shipped support for the TC39 Stage 3 decorators proposal. It's different from the old experimentalDecorators, more useful, and now the way to actually write decorators.
P.35Redux is overkill for most React apps. Zustand and Jotai cover 90% of real state management needs with a fraction of the boilerplate. Here's when to use each and how they actually work.
P.36ESLint 9 made flat config the default and deprecated the old .eslintrc format. If your project is still on the legacy config, here's what changed, why it's better, and how to migrate without breaking your setup.
P.37Adding multi-language support to a React app is straightforward when you pick the right library for your setup. Here's how react-i18next, next-intl, and Lingui differ, and which fits each project type.
P.38Three 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.39Command-line tools are underrated as developer products. TypeScript makes them maintainable. Here's the full picture: argument parsing, interactive prompts, output formatting, and distribution.
P.40The 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.41NestJS has been growing quietly for years. If your Node.js backend is a pile of Express middleware with no clear structure, NestJS offers a path forward without changing languages.
P.42AI 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.43WebGPU is now available across Chrome, Firefox, and Safari. It's not just a graphics API. It's a general-purpose GPU compute layer that changes what's possible in a browser tab.
P.44Standardized commit messages unlock automatic changelogs, version bumps, and release notes. Here's the full setup — from writing commits to shipping releases without manual steps.
P.45Three 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.46Manifest 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.47Local-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.48Three 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.49Two browser APIs that used to require JavaScript libraries are now available in all major browsers. Here's what the View Transitions API and scroll-driven animations can do, with working code.
P.50The 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.51Most E2E test suites start fast and grow painful. Playwright solves most of that, but only if you set it up right from the start. Here is what actually works in production.
P.52React 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.53Media 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.54If 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.55Google's crawler runs JavaScript, but not the same way a browser does. The gap between what your JavaScript app renders and what gets indexed is where most SPA SEO problems hide.
P.56PWAs got a second wind when iOS 16.4 unlocked push notifications and iOS 17 improved install behavior. Three years later, the gap between PWA and native is narrow enough to matter.
P.57The 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.58JavaScript error handling is broken by default — exceptions are untyped, async errors are easy to miss, and side effects are invisible in function signatures. Effect TS fixes all three. Here is how it works.
P.59Vuex was Vue's state management library for years. Pinia replaced it as the official recommendation and changed how Vue apps manage shared state. Here is how Pinia works and where it fits in a Vue 3 application.
P.60Hono started as a tiny router for Cloudflare Workers and grew into the default choice for edge APIs. Here is what it does well, where it fits, and why the 'runs everywhere' claim is actually true.
P.61Interaction 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.62Tauri 2.0 added iOS and Android support while keeping what made 1.x compelling: tiny binaries, Rust backend, and native OS webviews instead of a bundled Chromium. Here's how it works and when to use it.
P.63Drizzle ORM has become the go-to choice for TypeScript projects that want type safety without the overhead of a heavy ORM. Here's how it works, how to migrate from Prisma, and when to use it.
P.64Vitest runs faster, works natively with ESM and TypeScript, and uses the same API as Jest. If you're still on Jest in a Vite-based project, here's the case for switching and exactly how to do it.
P.65Biome is a Rust-based JavaScript toolchain that handles linting, formatting, and imports in a single binary. We've been running it in production projects since late 2025. Here's what the migration from ESLint and Prettier actually looks like.
P.66Not 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.67Most E2E test suites break as fast as the features they cover. Here's how to write Playwright tests that hold up when the UI changes, the data changes, and the team keeps shipping.
P.68Video 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.69EditorPickBun 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.70EditorPickWe 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.71Our 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.72Vue 3.6 introduces Vapor Mode, compiling templates directly to DOM operations and skipping the virtual DOM entirely. We break down the benchmarks, the tradeoffs, and what this means for the vdom debate.
P.73Anders 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.74Vite 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.75Remix 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.76jQuery 4.0.0 dropped on January 17, 2026 -- the first major version in nearly a decade. Here's what's new, why jQuery still matters, and who should care about this release.
P.77A CVSS 10.0 remote code execution vulnerability in React Server Components has been actively exploited in the wild. Here's the full breakdown of React2Shell, the follow-up DoS CVE, patching guidance, and lessons for React developers.
P.78EditorPickFrom 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.79EditorPickA comprehensive guide to React 19's new features including Server Components, Actions API, React Compiler, and the new hooks that are changing how we build React applications.
P.80TypeScript 5.8 brings improved type checking, direct Node.js execution, and better JavaScript interoperability. Here's everything developers need to know.