In particular, I often write about React, CSS, JavaScript, TypeScript, and Node.js. collected in chronological order.
VS Code already resolves {@link} for symbols the current file imports, and gives up on everything else. Go To Definition for JSDoc closes that gap today — and if enough projects adopt it, that is evidence TypeScript could support it natively.
A small VS Code extension for jumping from JSDoc {@link SymbolName} references to TypeScript workspace symbols without adding imports just for navigation.
Claude Code v2.1.152 quietly added `disallowed-tools` to Skill frontmatter. My first reaction was to file it as a 4th Skills lever for trimming initial context — that turned out to be wrong, but the thing it actually does is more interesting: it spends Claude's reasoning budget more carefully by shrinking the tool selection space.
What Claude Code actually loads into context at startup once Tool Search defers MCP and built-in tool definitions on demand — why the live window is far smaller than the raw totals imply, and why Skills (not MCP) is now the biggest line you can cut, plus the plugin and MCP-instruction levers that trim the rest.
A practical fix for TS1434 and other false TypeScript errors in MDX files by using a local tsconfig, the MDX TypeScript plugin, and remark-frontmatter.
Daily OSS activity digest — React, TanStack, Next.js ecosystem
Daily OSS activity digest — React, TanStack, Next.js ecosystem
Daily OSS activity digest — React, TanStack, Next.js ecosystem
Daily OSS activity digest — React, TanStack, Next.js ecosystem
Daily OSS activity digest — React, TanStack, Next.js ecosystem