How to debug babelJS transpiled code using node-inspector?

babeljs node-inspector
cuadraman picture cuadraman · Sep 22, 2015 · Viewed 10.3k times · Source

I am trying to use node-inspector debug a nodeJS app running with babel-node.

babel-node index.js --debug

Node-inspector works but it shows the source maps in the transpiled es5 instead of es6

enter image description here

Answer

Sushant Rao picture Sushant Rao · Mar 4, 2016

For babel 6, I used the require hook.

Follow these instructions to get babel register. https://babeljs.io/docs/setup/#babel_register

In your app.js or entrypoint to the application add 

require('babel-register')({
  sourceMaps: true
});

If you need to add other options as well, see - https://babeljs.io/docs/usage/options/#options

You should be able to use node-inspector & chrome to to debug your application

Related questions

Using Node.js require vs. ES6 import/export

In a project I'm collaborating on, we have two choices on which module system we can use: Importing modules using require, and exporting using module.exports and exports.foo. Importing modules using ES6 import, and exporting using ES6 export Are …

Read More
Babel 6 regeneratorRuntime is not defined

I'm trying to use async, await from scratch on Babel 6, but I'm getting regeneratorRuntime is not defined. .babelrc file { "presets": [ "es2015", "stage-0" ] } package.json file "devDependencies": { "babel-core": "^6.0.20", "babel-preset-es2015": "^6.0.15", "babel-preset-stage-0": "^6.0.15" } .js file "use strict"; async function foo() { await bar(); } function bar() { } …

Read More
Getting Unexpected Token Export

I am trying to run some ES6 code in my project but I am getting an unexpected token export error. export class MyClass { constructor() { console.log("es6"); } }

Read More