feat(react): remove deprecated code (#16981)

packages/react/index.ts

@@ -1,6 +1,5 @@
 export {
   extraEslintDependencies,
-  createReactEslintJson,
   extendReactEslintJson,
 } from './src/utils/lint';
 export { CSS_IN_JS_DEPENDENCIES } from './src/utils/styled';

packages/react/src/generators/application/schema.d.ts

@@ -9,10 +9,6 @@ export interface Schema {
   tags?: string;
   unitTestRunner?: 'jest' | 'vitest' | 'none';
   inSourceTests?: boolean;
-  /**
-   * @deprecated
-   */
-  babelJest?: boolean;
   e2eTestRunner: 'cypress' | 'none';
   linter: Linter;
   pascalCaseFiles?: boolean;

packages/react/src/utils/lint.ts

@@ -25,50 +25,3 @@ export const extendReactEslintJson = (json: Linter.Config) => {
     ...config,
   };
 };
-
-/**
- * @deprecated Use {@link extendReactEslintJson} instead.
- */
-export const createReactEslintJson = (
-  projectRoot: string,
-  setParserOptionsProject: boolean
-): Linter.Config => ({
-  extends: ['plugin:@nx/react', `${offsetFromRoot(projectRoot)}.eslintrc.json`],
-  ignorePatterns: ['!**/*'],
-  overrides: [
-    {
-      files: ['*.ts', '*.tsx', '*.js', '*.jsx'],
-      /**
-       * NOTE: We no longer set parserOptions.project by default when creating new projects.
-       *
-       * We have observed that users rarely add rules requiring type-checking to their Nx workspaces, and therefore
-       * do not actually need the capabilites which parserOptions.project provides. When specifying parserOptions.project,
-       * typescript-eslint needs to create full TypeScript Programs for you. When omitting it, it can perform a simple
-       * parse (and AST tranformation) of the source files it encounters during a lint run, which is much faster and much
-       * less memory intensive.
-       *
-       * In the rare case that users attempt to add rules requiring type-checking to their setup later on (and haven't set
-       * parserOptions.project), the executor will attempt to look for the particular error typescript-eslint gives you
-       * and provide feedback to the user.
-       */
-      parserOptions: !setParserOptionsProject
-        ? undefined
-        : {
-            project: [`${projectRoot}/tsconfig.*?.json`],
-          },
-      /**
-       * Having an empty rules object present makes it more obvious to the user where they would
-       * extend things from if they needed to
-       */
-      rules: {},
-    },
-    {
-      files: ['*.ts', '*.tsx'],
-      rules: {},
-    },
-    {
-      files: ['*.js', '*.jsx'],
-      rules: {},
-    },
-  ],
-});