Typescript -> Babel sourcemaps using webpack

Question

Copy paste from ts-loader issues as it might be more appropriate here:

How to pass the typescript sourcemaps to babel so the end sourcemap point to the original file and not the compiled typescript one?

Here's an example of my dev settings:

tsconfig.json:

{
  "compilerOptions": {
    "target": "es6",
    "jsx": "react",
    "noImplicitAny": false,
    "sourceMap": true
  },
  "exclude": ["node_modules", "gulpfile.js", "webpack.config.js", "server.js"]
}

webpack.dev.js:

var path = require("path");
var webpack = require("webpack");

module.exports = {
  devtool: "eval",
  entry: [
    "webpack-hot-middleware/client",
    "./src/app/index",
  ],
  output: {
    path: path.join(__dirname, "build"),
    filename: "app.js",
    publicPath: "/static/"
  },
  plugins: [
    new webpack.HotModuleReplacementPlugin(),
    new webpack.NoErrorsPlugin(),
    new webpack.ProvidePlugin({
      'window.fetch': 'exports?self.fetch!whatwg-fetch'
    })
  ],
  resolve: {
    extensions: ['', '.ts', '.tsx', '.js']
  },
  module: {
    noParse: [
      /\/sinon.js/
    ],
    preLoaders: [{
      test: /\.ts(x?)$/,
      loader: "tslint",
      exclude: /node_modules/
    }],
    loaders: [
      {
        test: /\.tsx?$/,
        loader: 'babel-loader!ts-loader',
        exclude: /node_modules/,
        include: path.join(__dirname, 'src')
      }
    ]
  }
};

kimsk · Accepted Answer · 2016-07-19 02:16:30Z

4

You can use source-map-loader for webpack. Here is my webpack.config.js:

module.exports = {
    entry: "./app.ts",
    output: {
        filename: "./bundle.js",
    },

    devtool: "source-map",

    resolve: {
        extensions: ["", ".webpack.js", ".web.js", ".ts", ".js"]
    },

    module: {
        loaders: [
            // ts -> ES6 -> babel -> ES5
            { test: /\.tsx?$/, loaders: ["babel-loader", "ts-loader"] }
        ],

        preLoaders: [
            { test: /\.js$/, loader: "source-map-loader" }
        ]
    }
};

And tsconfig.js:

{
    "compilerOptions": {
        "target": "es6",
        "sourceMap": true
    },
    "exclude": [
        "node_modules"
    ]
}

answered Jul 19, 2016 at 2:16

kimsk

2,23122 silver badges23 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

Paul Turner Over a year ago

I could not get this to work for Babel 7 and Webpack 4. The source maps generated reflect the transpiled output from the TypeScript compiler instead of the source files.

theOwl · Accepted Answer · 2021-06-17 19:59:35Z

2

Old issue, but if anyone else runs across this try setting devtool to a different value in the webpack config like:

devtool: 'inline-cheap-module-source-map'

Expected Output Per Setting: https://webpack.js.org/configuration/devtool/#root

answered Jun 17, 2021 at 19:59

theOwl

4411 gold badge3 silver badges9 bronze badges

Collectives™ on Stack Overflow

Typescript -> Babel sourcemaps using webpack

2 Answers 2

1 Comment

Comments

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

1 Comment

Comments

Your Answer

Sign up or log in

Post as a guest

Related