Next.js Framework for React Applications
View All Tags
My chat page had a Stop button that calls abortRun() on its AG-UI agent. Pressing it stopped the answer — and showed signal is aborted without reason in red, as if something had failed. That text is the browser's wording for a cancelled request: @ag-ui/client 1.0.4 ends a stopped run with its own RUN_ERROR event, code abort. Skipping that one code fixed it.
I ran npm run dev from an AI coding assistant, and Next.js 16.4.6 printed ✓ Generated AGENTS.md for AI agents and added an AGENTS.md file to the project — although I had created the app with --no-agents-md. It's the agentRules option of next dev, and agentRules: false in next.config.ts turns it off and removes the file.
After I updated Biome to 2.6.6 in a new Next.js app, biome check failed with five errors: lint/a11y/noSvgWithoutTitle, Alternative text title element cannot be empty, one for each sample SVG file in public. The template's own Biome didn't check SVG files; Biome 2.5 and later do. A <title> in the SVGs the page uses, and deleting the ones it doesn't, made the check clean.
After I updated Biome from 2.4.2 to 2.6.6 in a new Next.js app, biome check reported The configuration schema version does not match the CLI version 2.6.6, and that the use of the recommended field has been deprecated. Both point at biome.json, which create-next-app wrote for Biome 2.4.2. One command, biome migrate --write, updated it.
A fresh Next.js app from create-next-app 16.4.6, with ESLint, printed npm warn deprecated eslint@9.39.5: This version is no longer supported. ESLint 9 reached end of life on August 6, 2026. Updating to ESLint 10.14.0 removes the warning; two scoped overrides keep npm audit at zero, and npm still warns that three Next.js lint plugins list only ESLint 9.
A brand-new Next.js app reported 7 moderate severity vulnerabilities before I had written a line of code, and npm audit fix changed nothing. All seven were one advisory in minimatch, deep inside the ESLint tools, with the fixed version outside the range its parent package accepts. A scoped overrides entry in package.json fixed it.
After I updated a new Next.js app to TypeScript 7.0.2, npm run lint stopped with typescript-eslint does not support TS 7.0. TypeScript 7.0 ships without the compiler API that typescript-eslint reads code with. The TypeScript team's own fix is two npm aliases: TypeScript 6's API for ESLint, and TypeScript 7's tsc for everything else.
create-next-app refused to create my Next.js app in web/agent-chat-ui with The application path is not writable, please check folder permissions and try again. The permissions were fine. The parent folder, web, didn't exist yet, and create-next-app reports a missing parent folder the same way as a locked one. Creating web first fixed it.
Learn how to deploy a Next.js application on a Linux Ubuntu server and connect it to your custom domain. This guide covers server setup, app deployment, Nginx reverse proxy, SSL (HTTPS), and DNS configuration.
