这可以通过在t配置中启用noFallthroughCasesInSwitch选项来解决。json。有关更多信息，请参见此处的讨论。

{
  "compilerOptions": {
    "noFallthroughCasesInSwitch": true,
    ...
  },
  ...
}

对于任何好奇的人来说，上述解决方案并不能修复这个bug。它只是跳过运行下面的错误代码，如果没有提供，它会将建议的值分配给typescript编译器选项。tsconfig。默认情况下，从react脚本生成的json没有noFallthroughCasesInSwitch选项。添加该选项可以消除运行代码的需要。

// Some options when not present in the tsconfig.json will be assigned
// a suggested value which crashes the program
if (suggested != null) {
  if (parsedCompilerOptions[option] === undefined) {
    appTsConfig.compilerOptions[option] = suggested; // error here
    ...
  }
} 

编辑：

如果脚本与其他选项一起崩溃，并且您具有与我的问题中相同的stackTrack，您应该检查以下编译器选项是否在您的tsconfig.json中丢失

当未在tsconfig中指定时，这些是Typescript编译器选项的建议值。json

const compilerOptions = {
  // These are suggested values and will be set when not present in the
  // tsconfig.json
  target: {
    parsedValue: ts.ScriptTarget.ES5,
    suggested: 'es5',
  },
  lib: { suggested: ['dom', 'dom.iterable', 'esnext'] },
  allowJs: { suggested: true },
  skipLibCheck: { suggested: true },
  esModuleInterop: { suggested: true },
  allowSyntheticDefaultImports: { suggested: true },
  strict: { suggested: true },
  forceConsistentCasingInFileNames: { suggested: true },
  noFallthroughCasesInSwitch: { suggested: true },
  module: {
    parsedValue: ts.ModuleKind.ESNext,
    value: 'esnext',
    reason: 'for import() and import/export',
  },
  moduleResolution: {
    parsedValue: ts.ModuleResolutionKind.NodeJs,
    value: 'node',
    reason: 'to match webpack resolution',
  },
  resolveJsonModule: { value: true, reason: 'to match webpack loader' },
  isolatedModules: { value: true, reason: 'implementation limitation' },
  noEmit: { value: true },
  jsx: {
    parsedValue: ts.JsxEmit.React,
    suggested: 'react',
  },
  paths: { value: undefined, reason: 'aliased imports are not supported' },
};

您需要将这些选项显式添加到tsconfig。json，因此脚本可以跳过错误分支，避免崩溃。