All Questions
15 questions
6
votes
1
answer
2k
views
How to get VSCode to attach to nodemon started by NPM?
Can I have VSCode kick off my app using NPM run scripts and then attach to the resulting process to debug?
My project kicks off with nodemon via NPM script (to execute babel, etc). However, while the ...
3
votes
0
answers
810
views
Async debugging problem with node and vs code
My breakpoints in VS code keep jumping - I am using node.JS and when I run the debugger my breakpoint goes from line 30 approximately to line 130 or so at the bottom of the file with the export ...
10
votes
0
answers
439
views
Using source maps when debugging babel-watch output
Using babel-watch, when debugging through the Chrome inspector, I don't have source maps available.
When running the same code using babel-node, with the same .babelrc, source maps are available.
...
2
votes
1
answer
450
views
How do you get correct variable names in babel-node debugger?
npm i babel-cli babel-preset-env
echo '{"presets": ["env"]}' > .babelrc
printf "import u from 'util';\ndebugger;\nconsole.log(u);\n" > foo.es
babel-node --inspect-brk foo.es
Continue to ...
1
vote
3
answers
1k
views
JavaScript Development in ES6 With Debugging
I have been trying to find a way to write ES6 JavaScript code, with real-time debugging features.
The problem is that ES6 code needs transpiling before browsers can interpret it (easy with babel), ...
1
vote
2
answers
575
views
vue.js with vue-multilanguage My webpack compilate is not translated right
My webpack compilate is not transpiled into the right JS. It writes
exports default MultiLanguage
instead of
module.exports = { MultiLanguage: MultiLanguage};
My .bablerc
{
"presets": ["es2015", "...
1
vote
0
answers
785
views
Having nodemon and debugging both working in a WebStorm run configuration
This is a problem I have never really been able to sort and have come across a few times so I thought I'd ask on here to see if there is a solution.
I am currently building a NodeJS(koa) application ...
0
votes
1
answer
535
views
WebStorm Debug configuration for Koa/Node/js application using babel
I am currently trying to set up a run configuration for a Koa NodeJS application I am building within WebStorm in order to get debugging functionality and am not having any success.
I can get the ...
3
votes
2
answers
4k
views
How to debug node.js backend written in es6/es7?
I want to debug es7 source code directly. I found the only one working way to debug already transpired es5 code, but it is very inconvenient. I tried babel-node --inspect my_es7_file.js, but it doesn'...
2
votes
1
answer
531
views
Why does babel-node-debug not recognize the import command?
» babel-node-debug --presets es2015 ./updateChains.js
Node Inspector v0.12.10
Visit http://127.0.0.1:8080/?port=5858 to start debugging.
Debugging `./scripts/updateChains.js`
Debugger listening on [::...
5
votes
0
answers
426
views
Variable inspection for import/export not working in VS Code
My project is using node. I run my code thru babel and build with source maps. VS Code will hit breakpoints fine and I can step thru code correctly but if I use import statements it does not allow ...
0
votes
1
answer
902
views
Errors not shown with babel-node
I'm not sure why, but I just ran into a situation in which an object was undefined and I tried to call a property on that object. What happend was nothing, except that the console seems to be hanging (...
4
votes
0
answers
2k
views
Debugging ES6 Node.js application with babel-node
I have some jest tests for my application. Other js sources which are used by the tests are written in js ES6 with Flow. My goal is to debug the sources used by tests. When I debug them, however, the ...
5
votes
1
answer
1k
views
Debug es6 transpiled code using node-inspector or babel-node-debug
When I debug my node rest api, I try to use node-inspector
node-inspector
node --debug server.js
This way I can debug my api using localhost:3000/api...
If I use node-debug, there's no way. It ...
24
votes
9
answers
17k
views
vscode debug ES6 application
I have VSCode 0.5.0. I set the compilerOptions flag to "ES6" and the editor started recognizing my ES6 code as correct.
I have babel installed.
My Mocha tests use the babel compilers and my tests ...