{
  "context": "This evaluation assesses how well the engineer uses @tsconfig/bases React framework configuration packages to solve the TypeScript configuration generation problem. The focus is on proper usage of the @tsconfig/vite-react, @tsconfig/next, and @tsconfig/react-native packages.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "Uses @tsconfig/vite-react",
      "description": "Implementation correctly uses the @tsconfig/vite-react package by including it as a dependency and extending '@tsconfig/vite-react/tsconfig.json' (or equivalent path) in generated configurations for Vite React projects.",
      "max_score": 25
    },
    {
      "name": "Uses @tsconfig/next",
      "description": "Implementation correctly uses the @tsconfig/next package by including it as a dependency and extending '@tsconfig/next/tsconfig.json' (or equivalent path) in generated configurations for Next.js projects.",
      "max_score": 25
    },
    {
      "name": "Uses @tsconfig/react-native",
      "description": "Implementation correctly uses the @tsconfig/react-native package by including it as a dependency and extending '@tsconfig/react-native/tsconfig.json' (or equivalent path) in generated configurations for React Native projects.",
      "max_score": 25
    },
    {
      "name": "Framework detection logic",
      "description": "The detectFramework function correctly identifies the framework type by checking for the presence of specific package names in the dependencies or devDependencies of the package.json (e.g., 'next', 'react-native', 'vite' + 'react').",
      "max_score": 15
    },
    {
      "name": "Configuration merging",
      "description": "The generateTsConfig function properly merges custom compiler options with the base configuration structure, creating a valid tsconfig.json object that includes both the 'extends' field and any custom 'compilerOptions'.",
      "max_score": 10
    }
  ]
}