<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Shaun Nguyen</title><link>https://truongson.dev/en/tags/debugging/</link><description>Recent content in Debugging on Shaun Nguyen</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 02 Feb 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://truongson.dev/en/tags/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>Setup NextJS debug on VSCode Windows + MS Edge</title><link>https://truongson.dev/en/writing/nextjs-vscode/</link><pubDate>Mon, 02 Feb 2026 00:00:00 +0000</pubDate><guid>https://truongson.dev/en/writing/nextjs-vscode/</guid><description>&lt;p&gt;Damn, I got stucked when following &lt;a href="https://nextjs.org/docs/pages/building-your-application/configuring/debugging#debugging-with-vs-code"&gt;NextJS recommendation&lt;/a&gt;, because it only work on UNIX-like system which have shell that can run &lt;code&gt;.sh&lt;/code&gt; file. Totally bullshit.&lt;/p&gt;
&lt;p&gt;This instruction prefer Bun, because it is Typescript native and spin up dev quick. You can choose NPM or Yarn, or PNPM as your favorite package manager.&lt;/p&gt;
&lt;p&gt;After some conversation with Claude, I figure it out by edit the &lt;code&gt;program&lt;/code&gt; part of &lt;code&gt;Next.js: debug full stack&lt;/code&gt; to direct &lt;code&gt;next&lt;/code&gt; executable.&lt;/p&gt;</description></item></channel></rss>