This is a known issue, not related to Next.js, but it does affect Next.js development. This external service will check every file read, which has been reported to greatly increase Fast Refresh time with next dev. Note: Ensure Windows Defender is disabled on your machine. 'dev' : 'cross-env NODE_OPTIONS='-inspect' next dev' ,Ĭross-env will set the NODE_OPTIONS environment variable regardless of which platform you are on (including Mac, Linux, and Windows) and allow you to debug consistently across devices and operating systems. To get around this, install the cross-env package as a development dependency ( -D with npm and yarn) and replace the dev script with the following. Windows users may run into an issue when using NODE_OPTIONS='-inspect' as that syntax is not supported on Windows platforms. vscode/launch.json at the root of your project with the following content: will be replaced with the name of your application according to your package.json file). Debugging with VS CodeĬreate a file named. However, when I try to debug the app I encounter a few problems. After adding all the needed files I executed 'npm start' and the pages ran successfully on chrome. npm version is 6.14.9 and node.js version is v14.15.1. You can find more details in the Node.js Debugging Guide. I have Intellij IDEA Ultimate IDE (2020.2.4) and I created a new React App project using npx create-react-app. This documentation explains how you can debug your Next.js frontend and backend code with full source maps support using either the VS Code debugger or Chrome DevTools.Īny debugger that can attach to Node.js can also be used to debug a Next.js application.

React intellij debug