fix module resolution type in tsconfig

Author: KurtGokhan

config/webpack.config.js

@@ -53,10 +53,6 @@ const babelRuntimeRegenerator = require.resolve('@babel/runtime/regenerator', {
   paths: [babelRuntimeEntry],
 });
 
-// Some apps do not need the benefits of saving a web request, so not inlining the chunk
-// makes for a smoother build process.
-const shouldInlineRuntimeChunk = process.env.INLINE_RUNTIME_CHUNK === 'true';
-
 const emitErrorsAsWarnings = process.env.ESLINT_NO_DEV_ERRORS === 'true';
 const disableESLintPlugin = process.env.DISABLE_ESLINT_PLUGIN === 'true';
 const extractCss = process.env.EXTRACT_CSS === 'true';
@@ -204,6 +200,7 @@ const baseConfigFactory = function (webpackEnv) {
       ...entryObj,
     },
     output: {
+      clean: false,
       // The build folder.
       path: paths.appBuild,
       // Add /* filename */ comments to generated require()s in the output.

tsconfig.json

@@ -5,8 +5,8 @@
     "allowJs": true,
     "pretty": true,
     "declaration": false,
-    "module": "nodenext",
-    "moduleResolution": "nodenext",
+    "module": "ESNext",
+    "moduleResolution": "Bundler",
     "preserveSymlinks": true,
     "importHelpers": false,
     "strict": true,