v15.0.4

Patch Changes

• Fix a bundling issue causing eslint to throw an error. Update globals dep to ^17.0.0. (#267)

v15.0.3

Patch Changes

• Revert globals dependency back to ^16.0.0 (#264)

v15.0.2

Patch Changes

• deps: globals ^17.0.0 (#262)

v15.0.1

Patch Changes

• Fixes a bug that prevented configuring custom rules that rely on plugins (#254)

v15.0.0

Major Changes

• Configure explicit exports for all entrypoints (#248)

  This package now configures explicit exports in its package.json file for all entrypoints. Consumers previously importing from eslint-config-seek/base.js or eslint-config-seek/extensions.js should update their import statements to use the new explicit entrypoints:

  - import 'eslint-config-seek/base.js';
  + import 'eslint-config-seek/base';
  
  - import 'eslint-config-seek/extensions.js';
  + import 'eslint-config-seek/extensions';

• Upgrade @typescript-eslint/naming-convention rule from warn to error (#248)

  This rule enforces using PascalCase for typeLike declarations excluding enums (allowing leading underscores).

• Update eslint peer depenedency to ^9.22.0 (#248)

• Remove no-unused-vars rule exception for React namespace import (#248)

  The no-unused-vars rule exception for the React namespace import has been removed. This means that if you import the entire React namespace but do not use it in your code, ESLint will now flag it as an unused variable.

  This exception was originally added to accommodate older versions of React (prior to v17) where JSX syntax required the React namespace to be in scope. However, with the introduction of the new JSX Transform in React 17, this was no longer necessary. A temporary exception was made to ease the transition, but it has now been removed to encourage cleaner code.

  MIGRATION GUIDE:

  -import React from 'react';
  
  -import React, { useState } from 'react';
  +import { useState } from 'react';

Minor Changes

• Expose 2 Vitest-specific entrypoints: (#248)

  • eslint-config-seek/vitest: for general Vitest projects
  • eslint-config-seek/vitest/base: for Vitest projects not using React

  These are equivalent to the existing eslint-config-seek and eslint-config-seek/base entrypoints, but with Vitest-specific rules and settings applied instead of Jest-specific ones.

v14.7.0

Minor Changes

• Add types for root, /base and /extensions entrypoints (#247)

• Add eslint-plugin-import-zod to re-write Zod imports (#224)

  This plugin adds rules for rewriting Zod imports such as import { z } from "zod"; to import * as z from 'zod'; in order to reduce bundle sizes when using a bundler.

Patch Changes

• Publish with provenance (#241)

v14.6.0

Minor Changes

• Error on custom getters and setters (#227)

  The no-restricted-syntax rule is now preconfigured to ban custom getters and setters. Engineers typically expect property access to be a safer operation than method or function invocation. Throwing an error from a getter can cause confusion and unhandled promise rejections, which can lead to a crash on the server side if not appropriately configured. See the PR for more information.

  const obj = {
  - get prop() {
  + prop() {
      throw new Error('Badness!');
    },
  };

  A custom getter may be occasionally prescribed as the recommended approach to achieve desired behaviour. For example, this syntax can define a recursive object in Zod. In these rare scenarios, add an inline ignore and ensure that you do not throw an error within the getter.

  import * as z from 'zod';
  
  const Category = z.object({
    name: z.string(),
    // eslint-disable-next-line no-restricted-syntax -- Zod recursive type
    get subcategories() {
      return z.array(Category);
    },
  });

v14.5.3

Patch Changes

• deps: eslint-plugin-jest ^29.0.0 (#221)

• Update eslint-plugin-cypress to v5 (#217)

v14.5.2

Patch Changes

• Fix lint issue in [@typescript-eslint/naming-convention] rule. (#214)

v14.5.1

Patch Changes

• Disable @typescript-eslint/naming-convention rule for enums. (#212)