Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

ci(dev-deps): update all non-major dependencies #914

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

ci(dev-deps): update all non-major dependencies #914

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 1, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@cspell/dict-cryptocurrencies (source) 5.0.3 -> 5.0.4 age adoption passing confidence devDependencies patch
@eslint/compat 1.2.3 -> 1.2.4 age adoption passing confidence devDependencies patch
@rebeccastevens/eslint-config 3.3.4 -> 3.5.1 age adoption passing confidence devDependencies minor
@rollup/plugin-replace (source) 6.0.1 -> 6.0.2 age adoption passing confidence devDependencies patch
@rollup/plugin-typescript (source) 12.1.1 -> 12.1.2 age adoption passing confidence devDependencies patch
@types/node (source) 18.19.67 -> 18.19.68 age adoption passing confidence devDependencies patch
@vitest/eslint-plugin 1.1.13 -> 1.1.22 age adoption passing confidence devDependencies patch
codecov/codecov-action v5.0.7 -> v5.1.2 age adoption passing confidence action minor
eslint-import-resolver-typescript 3.6.3 -> 3.7.0 age adoption passing confidence devDependencies minor
eslint-plugin-eslint-plugin 6.3.2 -> 6.4.0 age adoption passing confidence devDependencies minor
eslint-plugin-import-x 4.4.3 -> 4.6.1 age adoption passing confidence devDependencies minor
eslint-plugin-jsdoc 50.6.0 -> 50.6.1 age adoption passing confidence devDependencies patch
eslint-plugin-n 17.14.0 -> 17.15.1 age adoption passing confidence devDependencies minor
eslint-vitest-rule-tester 0.6.1 -> 0.7.1 age adoption passing confidence devDependencies minor
knip (source) 5.38.3 -> 5.41.1 age adoption passing confidence devDependencies minor
lint-staged 15.2.10 -> 15.3.0 age adoption passing confidence devDependencies minor
markdownlint-cli2 0.15.0 -> 0.17.1 age adoption passing confidence devDependencies minor
node (source) 22.11.0 -> 22.12.0 age adoption passing confidence minor
pnpm (source) 9.14.4 -> 9.15.2 age adoption passing confidence packageManager minor
prettier (source) 3.4.1 -> 3.4.2 age adoption passing confidence devDependencies patch
rollup (source) 4.28.0 -> 4.29.1 age adoption passing confidence devDependencies minor
vite-tsconfig-paths 5.1.3 -> 5.1.4 age adoption passing confidence devDependencies patch

Release Notes

streetsidesoftware/cspell-dicts (@​cspell/dict-cryptocurrencies)

v5.0.4

Compare Source

Updates and Bug Fixes
eslint/rewrite (@​eslint/compat)

v1.2.4

Compare Source

RebeccaStevens/eslint-config-rebeccastevens (@​rebeccastevens/eslint-config)

v3.5.1

Compare Source

Bug Fixes
  • only use ts version of no-loop-func when using ts (48dc0b0)

v3.5.0

Compare Source

Bug Fixes
  • functional/no-conditional-statements: ignore import.meta.vitest conditions (4b6990d)
  • update import rules for apps (723a40d)
Features
  • add support for ReactRouter 7 (83cf882)

v3.4.0

Compare Source

Bug Fixes
Features
  • enforce non-sloppy imports for library code (0490a67)

3.3.5 (2024-12-14)

Bug Fixes

3.3.4 (2024-11-28)

Bug Fixes
  • ts/switch-exhaustiveness-check: considerDefaultExhaustiveForUnions: true (2e4b7c4)
  • yaml/quotes (94cf07b)

3.3.3 (2024-10-20)

Bug Fixes
  • only enforce max-classes-per-file when not functional (096d7ed)
  • use functional/no-class-inheritance over functional/no-classes (68fb811)

3.3.2 (2024-10-09)

Bug Fixes
  • updating naming-convention (a818739)

3.3.1 (2024-10-08)

Bug Fixes
  • add eslint-plugin-jsx-a11y (2e13bb6)

v3.3.5

Compare Source

Bug Fixes
rollup/plugins (@​rollup/plugin-replace)

v6.0.2

2024-12-15

Bugfixes
  • fix: add missing types for objectGuards option (#​1818)
rollup/plugins (@​rollup/plugin-typescript)

v12.1.2

2024-12-15

Bugfixes
  • fix: path validation issue in validatePaths function (#​1800)
vitest-dev/eslint-plugin-vitest (@​vitest/eslint-plugin)

v1.1.22

Compare Source

Bug Fixes
  • valid-title false positives when test.extend is used (#​584) (9c2670a)

v1.1.21

Compare Source

Bug Fixes
Performance Improvements
  • only build regexp ones for detecting expectations (#​608) (448650c)

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.20...v1.1.21

v1.1.20

Compare Source

Bug Fixes

What's Changed

New Contributors

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.19...v1.1.20

v1.1.19

Compare Source

Bug Fixes

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.18...v1.1.19

v1.1.18

Compare Source

Features

What's Changed

New Contributors

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.17...v1.1.18

v1.1.17

Compare Source

Bug Fixes
  • expect.hasAssertions() / expect.assertions() - Does not work when using expect() bound to current test (#​595) (efe79c9)

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.16...v1.1.17

v1.1.16

Compare Source

What's Changed

New Contributors

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.15...v1.1.16

v1.1.15

Compare Source

Bug Fixes
  • padding-around-expect-groups doesn't detect expectTypeOf as an expect clause (#​588) (1138003)

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.14...v1.1.15

v1.1.14

Compare Source

What's Changed

Full Changelog: vitest-dev/eslint-plugin-vitest@v1.1.13...v1.1.14

codecov/codecov-action (codecov/codecov-action)

v5.1.2

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.1.1..v5.1.2

v5.1.1

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.1.0..v5.1.1

v5.1.0

Compare Source

What's Changed

Full Changelog: https://github.com/codecov/codecov-action/compare/v5.0.7..v5.1.0

import-js/eslint-import-resolver-typescript (eslint-import-resolver-typescript)

v3.7.0

Compare Source

Minor Changes

  • #​326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

    Previously

    // eslint.config.js
module.exports = {
  settings: {
    'import-x/resolver': {
      typescript: {
        alwaysTryTypes: true,
      },
      // or
      require.resolve('eslint-import-resolver-typescript'):
        alwaysTryTypes: true,
      }
    }
  }
}

    Now

    // eslint.config.js
const {
  createTypeScriptImportResolver,
} = require('eslint-import-resolver-typescript')

module.exports = {
  settings: {
    'import-x/resolver-next': [
      createTypeScriptImportResolver({
        alwaysTryTypes: true,
      }),
    ],
  },
}

    Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

eslint-community/eslint-plugin-eslint-plugin (eslint-plugin-eslint-plugin)

v6.4.0

Compare Source

Features
un-ts/eslint-plugin-import-x (eslint-plugin-import-x)

v4.6.1

Compare Source

Patch Changes

v4.6.0

Compare Source

Minor Changes

  • #​209 46d2360 Thanks @​SukkaW! - When eslint-plugin-import-x was forked from eslint-plugin-import, we copied over the default resolver (which is eslint-import-resolver-node) as well. However, this resolver doesn't supports exports in the package.json file, and the current maintainer of the eslint-import-resolver-node (ljharb) doesn't have the time implementing this feature and he locked the issue https://github.com/import-js/eslint-plugin-import/issues/1810.

    So we decided to implement our own resolver that "just works". The new resolver is built upon the enhanced-resolve that implements the full Node.js Resolver Algorithm. The new resolver only implements the import resolver interface v3, which means you can only use it with ESLint Flat config. For more details about the import resolver interface v3, please check out #​192.

    In the next major version of eslint-plugin-import-x, we will remove the eslint-import-resolver-node and use this new resolver by default. In the meantime, you can try out this new resolver by setting the import-x/resolver-next option in your eslint.config.js file:

    // eslint.config.js
const eslintPluginImportX = require('eslint-plugin-import-x');
const { createNodeResolver } = eslintPluginImportX;

module.exports = {
  plugins: {
    'import-x': eslintPluginImportX,
  },
  settings: {
    'import-x/resolver-next': [
      // This is the new resolver we are introducing
      createNodeResolver({
        /**
         * The allowed extensions the resolver will attempt to find when resolving a module
         * By default it uses a relaxed extension list to search for both ESM and CJS modules
         * You can customize this list to fit your needs
         *
         * @​default ['.mjs', '.cjs', '.js', '.json', '.node']
         */
        extensions?: string[];
        /**
         * Optional, the import conditions the resolver will used when reading the exports map from "package.json"
         * By default it uses a relaxed condition list to search for both ESM and CJS modules
         * You can customize this list to fit your needs
         *
         * @​default ['default', 'module', 'import', 'require']
         */
        conditions: ['default', 'module', 'import', 'require'],
        // You can pass more options here, see the enhanced-resolve documentation for more details
        // https://github.com/webpack/enhanced-resolve/tree/v5.17.1?tab=readme-ov-file#resolver-options
      }),
      // you can add more resolvers down below
      require('eslint-import-resolver-typescript').createTypeScriptImportResolver(
        /** options of eslint-import-resolver-typescript */
      )
    ],
  },
};

    We do not plan to implement reading baseUrl and paths from the tsconfig.json file in this resolver. If you need this feature, please checkout eslint-import-resolver-typescript (also powered by enhanced-resolve), eslint-import-resolver-oxc (powered by oxc-resolver), eslint-import-resolver-next (also powered by oxc-resolver), or other similar resolvers.

Patch Changes

v4.5.1

Compare Source

Patch Changes

v4.5.0

Compare Source

Minor Changes
For eslint-plugin-import-x users

Like the ESLint flat config allows you to use js objects (e.g. import and require) as ESLint plugins, the new eslint-plugin-import-x resolver settings allow you to use js objects as custom resolvers through the new setting import-x/resolver-next:

// eslint.config.js
import { createTsResolver } from '#custom-resolver';
const { createOxcResolver } = require('path/to/a/custom/resolver');

const resolverInstance = new ResolverFactory({});
const customResolverObject = {
  interfaceVersion: 3,
  name: 'my-custom-eslint-import-resolver',
  resolve(modPath, sourcePath) {
    const path = resolverInstance.resolve(modPath, sourcePath);
    if (path) {
      return {
        found: true,
        path
      };
    }

    return {
      found: false,
      path: null
    }
  };
};

module.exports = {
  settings: {
    // multiple resolvers
    'import-x/resolver-next': [
      customResolverObject,
      createTsResolver(enhancedResolverOptions),
      createOxcResolver(oxcOptions),
    ],
    // single resolver:
    'import-x/resolver-next': [createOxcResolver(oxcOptions)]
  }
}

The new import-x/resolver-next no longer accepts strings as the resolver, thus will not be compatible with the ESLint legacy config (a.k.a. .eslintrc). Those who are still using the ESLint legacy config should stick with import-x/resolver.

In the next major version of eslint-plugin-import-x (v5), we will rename the currently existing import-x/resolver to import-x/resolver-legacy (which allows the existing ESLint legacy config users to use their existing resolver settings), and import-x/resolver-next will become the new import-x/resolver. When ESLint v9 (the last ESLint version with ESLint legacy config support) reaches EOL in the future, we will remove import-x/resolver-legacy.

We have also made a few breaking changes to the new resolver API design, so you can't use existing custom resolvers directly with import-x/resolver-next:

// When migrating to `import-x/resolver-next`, you CAN'T use legacy versions of resolvers directly:
module.exports = {
  settings: {
    // THIS WON'T WORK, the resolver interface required for `import-x/resolver-next` is different.
    'import-x/resolver-next': [
       require('eslint-import-resolver-node'),
       require('eslint-import-resolver-webpack'),
       require('some-custom-resolver')
    ];
  }
}

For easier migration, the PR also introduces a compat utility importXResolverCompat that you can use in your eslint.config.js:

// eslint.config.js
import eslintPluginImportX, { importXResolverCompat } from 'eslint-plugin-import-x';
// or
const eslintPluginImportX = require('eslint-plugin-import-x');
const { importXResolverCompat } = eslintPluginImportX;

module.exports = {
  settings: {
    // THIS WILL WORK as you have wrapped the previous version of resolvers with the `importXResolverCompat`
    'import-x/resolver-next': [
       importXResolverCompat(require('eslint-import-resolver-node'), nodeResolveOptions),
       importXResolverCompat(require('eslint-import-resolver-webpack'), webpackResolveOptions),
       importXResolverCompat(require('some-custom-resolver'), { option1: true, option2: '' })
    ];
  }
}
For custom import resolver developers

This is the new API design of the resolver interface:

export interface NewResolver {
  interfaceVersion: 3;
  name?: string; // This will be included in the debug log
  resolve: (modulePath: string, sourceFile: string) => ResolvedResult;
}

// The `ResultNotFound` (returned when not resolved) is the same, no changes
export interface ResultNotFound {
  found: false;
  path?: undefined;
}

// The `ResultFound` (returned resolve result) is also the same, no changes
export interface ResultFound {
  found: true;
  path: string | null;
}

export type ResolvedResult = ResultNotFound | ResultFound;

You will be able to import NewResolver from eslint-plugin-import-x/types.

The most notable change is that eslint-plugin-import-x no longer passes the third argument (options) to the resolve function.

We encourage custom resolvers' authors to consume the options outside the actual resolve function implementation. You can export a factory function to accept the options, this factory function will then be called inside the eslint.config.js to get the actual resolver:

// custom-resolver.js
exports.createCustomResolver = (options) => {
  // The options are consumed outside the `resolve` function.
  const resolverInstance = new ResolverFactory(options);

  return {
    name: 'custom-resolver',
    interfaceVersion: 3,
    resolve(mod, source) {
      const found = resolverInstance.resolve(mod, {});

      // Of course, you still have access to the `options` variable here inside
      // the `resolve` function. That's the power of JavaScript Closures~
    }
  }
};

// eslint.config.js
const { createCustomResolver } = require('custom-resolver')

module.exports = {
  settings: {
    'import-x/resolver-next': [
       createCustomResolver(options)
    ];
  }
}

This allows you to create a reusable resolver instance to improve the performance. With the existing version of the resolver interface, because the options are passed to the resolver function, you will have to create a resolver instance every time the resolve function is called:

module.exports = {
  interfaceVersion: 2,
  resolve(mod, source) {
    // every time the `resolve` function is called, a new instance is created
    // This is very slow
    const resolverInstance = ResolverFactory.createResolver({});
    const found = resolverInstance.resolve(mod, {});
  },
};

With the factory function pattern, you can create a resolver instance beforehand:

exports.createCustomResolver = (options) => {
  // `enhance-resolve` allows you to create a reusable instance:
  const resolverInstance = ResolverFactory.createResolver({});
  const resolverInstance = enhanceResolve.create({});

  // `oxc-resolver` also allows you to create a reusable instance:
  const resolverInstance = new ResolverFactory({});

  return {
    name: "custom-resolver",
    interfaceVersion: 3,
    resolve(mod, source) {
      // the same re-usable instance is shared across `resolve` invocations.
      // more performant
      const found = resolverInstance.resolve(mod, {});
    },
  };
};
Patch Changes
gajus/eslint-plugin-jsdoc (eslint-plugin-jsdoc)

[v50.6.1](https://redirect.github.com/gajus/eslint-plug

Configuration

📅 Schedule: Branch creation - "* 0-3 1 * *" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added 💙 Renovate Type: Maintenance Generic maintenance tasks, e.g., package updates. labels Jan 1, 2025
@graphite-app Graphite App
Copy link

graphite-app bot commented Jan 1, 2025

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

  • Status: Merge Queue - adds this PR to the back of the merge queue
  • Status: Hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
💙 Renovate Type: Maintenance Generic maintenance tasks, e.g., package updates.
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants