Skip to content

v15.0.0

Choose a tag to compare

@seek-oss-ci seek-oss-ci released this 10 Dec 03:03
· 34 commits to master since this release
e88b28b

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.