From 81ca8537d10b41dc17e9ff09f9551964086f139d Mon Sep 17 00:00:00 2001
From: Nworm <35765846+1574242600@users.noreply.github.com>
Date: Sun, 15 Aug 2021 07:18:36 +0800
Subject: [PATCH] Fix wrong devtool example (#1362)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 9592a7d73..5db1281b2 100644
--- a/README.md
+++ b/README.md
@@ -187,7 +187,7 @@ First, for `ts-loader` to produce **sourcemaps**, you will need to set the [tsco
 Second, you need to set the `devtool` option in your `webpack.config.js` to support the type of sourcemaps you want. To make your choice have a read of the [`devtool` webpack docs](https://webpack.js.org/configuration/devtool/). You may be somewhat daunted by the choice available. You may also want to vary the sourcemap strategy depending on your build environment. Here are some example strategies for different environments:
 
 * `devtool: 'inline-source-map'` - Solid sourcemap support; the best "all-rounder". Works well with karma-webpack (not all strategies do)
-* `devtool: 'cheap-module-eval-source-map'` - Best support for sourcemaps whilst debugging.
+* `devtool: 'eval-cheap-module-source-map'` - Best support for sourcemaps whilst debugging.
 * `devtool: 'source-map'` - Approach that plays well with UglifyJsPlugin; typically you might use this in Production
 
 ### Code Splitting and Loading Other Resources