* Changed Webpack to target ES2015 (as part of my shift to es2015 as …

…the target for all my projects/libs). [the project required es6 anyway due to mobx 5, since it uses es2015 proxies, which are unable to be fully polyfilled]
canonical-debate-lab · Dec 12, 2019 · 2a51be8 · 2a51be8
1 parent 263f6c1
commit 2a51be8
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 1 deletion.
diff --git a/Scripts/Build/WebpackConfig.ts b/Scripts/Build/WebpackConfig.ts
@@ -206,6 +206,8 @@ webpackConfig.module.rules = [
 					{
 						loose: true,
 						exclude: DEV ? ['babel-plugin-transform-async-to-generator', 'babel-plugin-transform-regenerator'] : [],
+						// targets: {esmodules: true}, // target es2015
+						targets: { node: '6.5' }, // target es2015
 					},
 				],
 				'@babel/react',

diff --git a/tsconfig.json b/tsconfig.json
@@ -46,7 +46,7 @@
 		//"target": "ES5",
 		//"target": "es2015",
 		//"target": "es2017",
-		"target": "esnext",
+		"target": "esnext", // babel targets es2015 (ie. transpiles our code to it), so it's fine for TS to target es-next
 		"lib": [
 			"es5",
 			"es6",