If you downgrade to Node 6 (I tested with 6.9.4), it starts working correctly. brew install node npm i -g pnpmx.x.x make sure x.x.x version matched the version of my project Then go to use /usr/local/pin/pnpm under 'Preferences' -> 'Languages & Frameworks' -> 'Node. My expectation is, that WebStorm will have same issue. I solved the problem by installing, node and npm then pnpm as global under my Mac that I do not have before. To do that, you need to create a separate JavaScript Debug configuration in addition to the Node.js configuration and run these two configurations together. Solution 3ĭebug breakpoints not work in my PhpStorm 2016.3.2 with NodeJS 7.7.x. With WebStorm, you can debug the server-side code of a Node.js application together with its client-side JavaScript code. Wanted to chime in and say that it is absolutely critical that you use -debug-brk and not -debug with getting WebStorm breakpoints to work for remote debugging as well as running the server directly from webstorm.Įven though -debug-brk technically just stops and waits for the debugger to join, and -debug allows you to join later, my breakpoints failed with just -debug no matter the remote configuration I tried.Īs far as I can tell, connecting WebStorm 11 to a node.js server on the debug port, with only -debug, will connect but fail to load any breakpoints that work. You can do many things that will help you explore the code and understand where the bug is. Reconnect automatically Select this checkbox to enable the WebStorm built-in debugger to re-attach to a running Node.js process after the code of the application is changed. You can put breakpoints right in your source code (no more debugger and console.log () statements), which can be written in JavaScript or TypeScript. Node.js < 8 started with -debug: choose this option to use the V8 Debugging Protocol (also known as Legacy Protocol). You can do it by going to Help -> Find Actionįor me disabling this option made debugging anything node-related much faster and much more predictable. WebStorm makes it easier to debug Node.js apps. (\index-compiled.js:3:12)Īt Object.Module._extensions.js (module.Try to disable js.debugger.v8. in WebStorm registry. "C:\Program Files\nodejs\node.exe" -debug-brk=45287 -nolazy index-compiled.jsĪt nInThisContext (vm.js:53:16)Īt Object.Module._extensions.js (module.js:404:10)Īt Function.Module._load (module.js:300:12)Īt Object. Error on debug, I am running against the index-compiled.js during debugĬ:\Program Files (x86)\JetBrains\WebStorm 11.0.3\bin\runnerw.exe" "babel-plugin-transform-decorators-legacy": "^1.3.4", "test": "echo \"Error: no test specified\" & exit 1" # sourceMappingURL=index-compiled.js.map Again, I have tried the other StackOverflow suggestions with no luck at this point. The code should speak for itself, and I appreciate any thoughts on how to resolve it. Alternatively, for npm version 5.1 and earlier, install the create-react-app package yourself by running npm install -g create-react-app in the Terminal Alt+F12. From the create-react-app list, select npx create-react-app. I am using Node.js 5x, Babel 6, and I have a File Watcher setup to do the Babel transforms on the fly. Select a configured interpreter from the list or choose Add to configure a new one. Essentially I am trying to use the import/export module functionality with the package.json and bar.js code below. 1 Answer Sorted by: 17 You can modify your script as follows: 'debug': 'nodemon -exec \'node -inspect-brk0.0.0.0:9229 -require ts-node/register src/app. I am having an "Unexpected token export" issue in Webstorm that has not been solved by the other StackOverflow posts. With WebStorm, you can debug the server-side code of a Node.js application together with its client-side JavaScript code.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |