<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0">
  <channel>
    <title>dev-knowledge</title>
    <link>https://web-site-38o.pages.dev</link>
    <description>In-depth technical articles on Claude Code, MCP, agent development, Rust, and embedded systems.</description>
    <item>
      <title>PowerShell Where-Object Fails from Bash? It Is Usually Variable Expansion</title>
      <link>https://web-site-38o.pages.dev/articles/powershell-bash-variable-expansion-where-object/</link>
      <description>Why PowerShell commands with Where-Object and $_ break when launched through Bash, and how to avoid cross-shell variable expansion bugs.</description>
      <language>en</language>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/powershell-bash-variable-expansion-where-object/</guid>
    </item>
    <item>
      <title>Bash経由のPowerShell Where-Objectが壊れる原因は変数展開</title>
      <link>https://web-site-38o.pages.dev/ja/articles/powershell-bash-variable-expansion-where-object/</link>
      <description>BashやGit BashからPowerShellのWhere-Objectを呼ぶ時に、$_や$変数が先に展開されて壊れる原因と回避策を解説します。</description>
      <language>ja</language>
      <pubDate>Tue, 30 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/powershell-bash-variable-expansion-where-object/</guid>
    </item>
    <item>
      <title>VS Code Says Cannot Find setTimeout but tsc Passes: Add types node</title>
      <link>https://web-site-38o.pages.dev/articles/typescript-vscode-cannot-find-settimeout-tsc-passes/</link>
      <description>Why VS Code TypeScript can report missing Node globals while tsc passes, and how explicit types: node fixes the language server.</description>
      <language>en</language>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/typescript-vscode-cannot-find-settimeout-tsc-passes/</guid>
    </item>
    <item>
      <title>tscは通るのにVS CodeだけsetTimeoutが見つからない時はtypes nodeを見る</title>
      <link>https://web-site-38o.pages.dev/ja/articles/typescript-vscode-cannot-find-settimeout-tsc-passes/</link>
      <description>TypeScriptでtscは通るのにVS CodeだけNode.jsのグローバル型を見失う時に、types: [node]で直す理由を解説します。</description>
      <language>ja</language>
      <pubDate>Mon, 29 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/typescript-vscode-cannot-find-settimeout-tsc-passes/</guid>
    </item>
    <item>
      <title>Safe Path Containment on Windows in Node.js: Avoid startsWith Checks</title>
      <link>https://web-site-38o.pages.dev/articles/windows-path-containment-validation-nodejs/</link>
      <description>How to validate that a user path stays inside a root directory on Windows without being fooled by drive-relative, UNC, case, or traversal paths.</description>
      <language>en</language>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/windows-path-containment-validation-nodejs/</guid>
    </item>
    <item>
      <title>Node.jsでWindowsパスの範囲チェックをstartsWithで書かない</title>
      <link>https://web-site-38o.pages.dev/ja/articles/windows-path-containment-validation-nodejs/</link>
      <description>Windowsでユーザー指定パスがroot配下にあるかを、drive-relative、UNC、大小文字、.. traversalに騙されず検証する方法です。</description>
      <language>ja</language>
      <pubDate>Sun, 28 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/windows-path-containment-validation-nodejs/</guid>
    </item>
    <item>
      <title>Next.js localStorage Hydration: initializeWithValue false Is Not the Whole Fix</title>
      <link>https://web-site-38o.pages.dev/articles/nextjs-localstorage-hydration-guard-usehooks-ts/</link>
      <description>How to avoid Next.js localStorage hydration bugs with usehooks-ts, typed defaults, dependency arrays, and a guard for effects derived from stored values.</description>
      <language>en</language>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/nextjs-localstorage-hydration-guard-usehooks-ts/</guid>
    </item>
    <item>
      <title>Next.jsのlocalStorage hydrationはinitializeWithValue falseだけでは足りない</title>
      <link>https://web-site-38o.pages.dev/ja/articles/nextjs-localstorage-hydration-guard-usehooks-ts/</link>
      <description>Next.jsでusehooks-tsのuseLocalStorageを使う時に、hydration前のdefault値でeffectが走る問題とguardの入れ方を解説します。</description>
      <language>ja</language>
      <pubDate>Sat, 27 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/nextjs-localstorage-hydration-guard-usehooks-ts/</guid>
    </item>
    <item>
      <title>Writing Windows Paths to JSON from Git Bash? Avoid inline node -e and printf</title>
      <link>https://web-site-38o.pages.dev/articles/git-bash-json-backslash-escaping-windows/</link>
      <description>Why Windows backslashes can turn into tabs when writing JSON through Git Bash inline commands, and why file-based scripts are safer.</description>
      <language>en</language>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/git-bash-json-backslash-escaping-windows/</guid>
    </item>
    <item>
      <title>Git BashでWindowsパス入りJSONを書く時はinline node -eとprintfを避ける</title>
      <link>https://web-site-38o.pages.dev/ja/articles/git-bash-json-backslash-escaping-windows/</link>
      <description>Git BashでWindowsパス入りJSONを書く時に、バックスラッシュがタブ化する問題と、script fileに逃がす安全策を解説します。</description>
      <language>ja</language>
      <pubDate>Fri, 26 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/git-bash-json-backslash-escaping-windows/</guid>
    </item>
    <item>
      <title>Node.js on OneDrive: Move node_modules with a Windows Junction</title>
      <link>https://web-site-38o.pages.dev/articles/windows-onedrive-node-modules-junction/</link>
      <description>How to keep a Node.js project inside OneDrive while moving node_modules to an external folder with a Windows junction.</description>
      <language>en</language>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/windows-onedrive-node-modules-junction/</guid>
    </item>
    <item>
      <title>OneDrive上のNode.js開発はnode_modulesをjunctionで外へ逃がす</title>
      <link>https://web-site-38o.pages.dev/ja/articles/windows-onedrive-node-modules-junction/</link>
      <description>WindowsのOneDrive配下でNode.js開発が壊れる時に、node_modulesを外部フォルダへ移してjunctionで戻す手順を解説します。</description>
      <language>ja</language>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/windows-onedrive-node-modules-junction/</guid>
    </item>
    <item>
      <title>Next.js routes-manifest.json Missing? Check for Parallel next build First</title>
      <link>https://web-site-38o.pages.dev/articles/nextjs-routes-manifest-missing-parallel-build/</link>
      <description>A practical guide to diagnosing missing .next/routes-manifest.json errors caused by concurrent next build processes writing to the same .next directory.</description>
      <language>en</language>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/nextjs-routes-manifest-missing-parallel-build/</guid>
    </item>
    <item>
      <title>Next.jsでroutes-manifest.jsonが見つからない時は並列next buildを先に疑う</title>
      <link>https://web-site-38o.pages.dev/ja/articles/nextjs-routes-manifest-missing-parallel-build/</link>
      <description>Next.jsの.next/routes-manifest.json欠落エラーが、設定ミスではなく同じ.nextへ並列next buildした競合で起きるケースを解説します。</description>
      <language>ja</language>
      <pubDate>Thu, 25 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/nextjs-routes-manifest-missing-parallel-build/</guid>
    </item>
    <item>
      <title>Use PowerShell New-Item for node_modules Junctions on Windows</title>
      <link>https://web-site-38o.pages.dev/articles/powershell-node-modules-junction-new-item/</link>
      <description>Why PowerShell New-Item -ItemType Junction is safer than mklink for node_modules junctions, especially in Unicode Windows paths.</description>
      <language>en</language>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/powershell-node-modules-junction-new-item/</guid>
    </item>
    <item>
      <title>node_modulesのjunctionはmklinkよりPowerShell New-Itemで作る</title>
      <link>https://web-site-38o.pages.dev/ja/articles/powershell-node-modules-junction-new-item/</link>
      <description>Windowsでnode_modules junctionを作る時に、mklinkではなくPowerShellのNew-Item -ItemType Junctionを使う理由を解説します。</description>
      <language>ja</language>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/powershell-node-modules-junction-new-item/</guid>
    </item>
    <item>
      <title>MCP stdio Server Logging: Keep Logs on stderr, Not stdout</title>
      <link>https://web-site-38o.pages.dev/articles/mcp-stdio-server-logging-stderr/</link>
      <description>Why MCP stdio servers should avoid console.log, keep stdout clean for JSON-RPC, and send diagnostic logs to stderr instead.</description>
      <language>en</language>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/mcp-stdio-server-logging-stderr/</guid>
    </item>
    <item>
      <title>MCP stdioサーバーのログはstderrへ: stdoutを汚さない設計</title>
      <link>https://web-site-38o.pages.dev/ja/articles/mcp-stdio-server-logging-stderr/</link>
      <description>MCP stdioサーバーでconsole.logを避け、ログをstderrへ出すべき理由を、stdoutがJSON-RPC通信路になる仕組みから解説します。</description>
      <language>ja</language>
      <pubDate>Wed, 24 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/mcp-stdio-server-logging-stderr/</guid>
    </item>
    <item>
      <title>Vite Build Crashed After Emit? Check Fresh Output Before Failing the Build</title>
      <link>https://web-site-38o.pages.dev/articles/vite-node-build-post-emit-crash-check/</link>
      <description>How to distinguish a real Vite build failure from a Windows post-emit crash by cleaning dist and checking fresh generated files.</description>
      <language>en</language>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/vite-node-build-post-emit-crash-check/</guid>
    </item>
    <item>
      <title>Vite buildが成功表示後に落ちる時はdistの鮮度で判定する</title>
      <link>https://web-site-38o.pages.dev/ja/articles/vite-node-build-post-emit-crash-check/</link>
      <description>WindowsでVite buildがemit後にクラッシュする時に、古いdistを成功扱いしないための鮮度チェック手順を解説します。</description>
      <language>ja</language>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/vite-node-build-post-emit-crash-check/</guid>
    </item>
    <item>
      <title>Designing an MCP Markdown Knowledge Server: Why It Should Not Return HTML</title>
      <link>https://web-site-38o.pages.dev/articles/mcp-markdown-knowledge-server-design/</link>
      <description>How to design an MCP server for a Markdown knowledge base, why raw Markdown is better than HTML, and how to share one source across clients.</description>
      <language>en</language>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/mcp-markdown-knowledge-server-design/</guid>
    </item>
    <item>
      <title>MCPサーバーでMarkdown知識ベースを配信する設計: HTMLに変換しない理由</title>
      <link>https://web-site-38o.pages.dev/ja/articles/mcp-markdown-knowledge-server-design/</link>
      <description>MCPサーバーでMarkdown知識ベースを扱うとき、HTMLへ変換せずraw Markdownを返す設計がなぜ保守しやすいかを解説します。</description>
      <language>ja</language>
      <pubDate>Tue, 23 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/mcp-markdown-knowledge-server-design/</guid>
    </item>
    <item>
      <title>Why only next dev breaks CSS: it was NODE_ENV=production</title>
      <link>https://web-site-38o.pages.dev/articles/next-dev-css-parse-error-node-env-production/</link>
      <description>Why next build passes but next dev fails with a CSS parse error in Next.js, how to detect NODE_ENV pollution, and how to fix it for good.</description>
      <language>en</language>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/next-dev-css-parse-error-node-env-production/</guid>
    </item>
    <item>
      <title>next devだけCSSが壊れる原因はNODE_ENV=productionだった</title>
      <link>https://web-site-38o.pages.dev/ja/articles/next-dev-css-parse-error-node-env-production/</link>
      <description>Next.jsでnext buildは通るのにnext devだけCSSパースエラーになる原因と、NODE_ENV汚染の調べ方・直し方を解説します。</description>
      <language>ja</language>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/next-dev-css-parse-error-node-env-production/</guid>
    </item>
    <item>
      <title>Cloudflare Pages Git Integration or Direct Upload? Decide Before You Create the Project</title>
      <link>https://web-site-38o.pages.dev/articles/cloudflare-pages-git-vs-direct-upload/</link>
      <description>How to choose between Cloudflare Pages Git integration and Wrangler Direct Upload before project creation, and why the choice affects deployment workflow.</description>
      <language>en</language>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/cloudflare-pages-git-vs-direct-upload/</guid>
    </item>
    <item>
      <title>Cloudflare PagesはGit連携かDirect Uploadかを作成前に決める</title>
      <link>https://web-site-38o.pages.dev/ja/articles/cloudflare-pages-git-vs-direct-upload/</link>
      <description>Cloudflare PagesのGit連携とWrangler Direct Uploadの違い、production/previewの扱い、選び方を解説します。</description>
      <language>ja</language>
      <pubDate>Mon, 22 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/cloudflare-pages-git-vs-direct-upload/</guid>
    </item>
    <item>
      <title>5 Pitfalls of Next.js output: export and How to Avoid Them</title>
      <link>https://web-site-38o.pages.dev/articles/nextjs-static-export-pitfalls/</link>
      <description>Five common gotchas when exporting a Next.js 15 app with output: export — force-static metadata routes, no next/og, trailingSlash, and next/image — with fixes.</description>
      <language>en</language>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/nextjs-static-export-pitfalls/</guid>
    </item>
    <item>
      <title>Next.jsのoutput: exportで詰まる5つの罠と回避策</title>
      <link>https://web-site-38o.pages.dev/ja/articles/nextjs-static-export-pitfalls/</link>
      <description>Next.js 15をoutput: exportで静的書き出しする際にハマるforce-static必須・next/og非対応・trailingSlash・next/imageなど5つの罠と回避策を実例で解説します。</description>
      <language>ja</language>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/nextjs-static-export-pitfalls/</guid>
    </item>
    <item>
      <title>Claude Code MCP Server Not Loading? Check Config Scope, Restart, and Tool Names</title>
      <link>https://web-site-38o.pages.dev/articles/claude-code-mcp-config-not-loading/</link>
      <description>A focused checklist for Claude Code MCP servers that do not appear or do not respond after editing configuration.</description>
      <language>en</language>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/articles/claude-code-mcp-config-not-loading/</guid>
    </item>
    <item>
      <title>Claude CodeでMCPサーバーが出ない時に見る設定・再起動・ツール名</title>
      <link>https://web-site-38o.pages.dev/ja/articles/claude-code-mcp-config-not-loading/</link>
      <description>Claude CodeでMCPサーバーを設定したのに出ない時に、設定場所、絶対パス、再起動、mcp__ツール名を確認する手順です。</description>
      <language>ja</language>
      <pubDate>Sun, 21 Jun 2026 00:00:00 GMT</pubDate>
      <guid>https://web-site-38o.pages.dev/ja/articles/claude-code-mcp-config-not-loading/</guid>
    </item>
  </channel>
</rss>