Skip to content

chore(deps): update all non-major dependencies #156

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
Merged
merged 2 commits into from
Dec 5, 2024
Merged

chore(deps): update all non-major dependencies #156

merged 2 commits into from
Dec 5, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 30, 2024 •
edited
Loading

This PR contains the following updates:

Package Change Age Adoption Passing Confidence Type Update
@swc/core (source) ^1.7.42 -> ^1.10.0 age adoption passing confidence devDependencies minor
@typescript-eslint/eslint-plugin (source) ^8.12.2 -> ^8.17.0 age adoption passing confidence devDependencies minor
eslint (source) ^9.13.0 -> ^9.16.0 age adoption passing confidence devDependencies minor
eslint-import-resolver-typescript ^3.6.3 -> ^3.7.0 age adoption passing confidence devDependencies minor
eslint-plugin-import-x ^4.4.0 -> ^4.5.0 age adoption passing confidence devDependencies minor
jiti ^2.3.3 -> ^2.4.1 age adoption passing confidence dependencies minor
node (source) 22.11.0 -> 22.12.0 age adoption passing confidence minor
pnpm (source) 9.12.3 -> 9.14.4 age adoption passing confidence minor
prettier (source) ^3.3.3 -> ^3.4.2 age adoption passing confidence devDependencies minor
typescript (source) ^5.6.3 -> ^5.7.2 age adoption passing confidence devDependencies minor
typescript-eslint (source) ^8.12.2 -> ^8.17.0 age adoption passing confidence devDependencies minor

Release Notes

swc-project/swc (@​swc/core)

v1.10.0

Compare Source

Bug Fixes
Features
Miscellaneous Tasks
Refactor

v1.9.3

Compare Source

Bug Fixes
Documentation
Features
Miscellaneous Tasks
Performance
Refactor

v1.9.2

Compare Source

Bug Fixes
Features

v1.9.1

Compare Source

Bug Fixes

v1.9.0

Compare Source

Bug Fixes
Features
Miscellaneous Tasks

v1.8.0

Compare Source

Bug Fixes

  • (es/typescript) Handle multiline type parameters in async arrow functions (#​9704) (c5ed19c)

  • (es/typescript) Handle ASI hazards in fast type strip (#​9707) (c135f71)

Features
Performance
typescript-eslint/typescript-eslint (@​typescript-eslint/eslint-plugin)

v8.17.0

Compare Source

🚀 Features
  • eslint-plugin: [prefer-promise-reject-errors] options to allow any and unknown (#​10392)
🩹 Fixes
  • eslint-plugin: [promise-function-async] handle function overloading (#​10304)
  • eslint-plugin: remove references to "extendDefaults" in no-restricted-types (#​10401)
  • eslint-plugin: [no-unnecessary-template-expressions] allow template expressions used to make trailing whitespace visible (#​10363)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.16.0

Compare Source

🚀 Features
  • eslint-plugin: [no-base-to-string] check Array.prototype.join (#​10287)
  • eslint-plugin: [max-params] add function overload and function type support (#​10312)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.15.0

Compare Source

🚀 Features
  • eslint-plugin: [prefer-nullish-coalescing] fix detection of ignoreConditionalTests involving boolean ! operator (#​10299)
  • eslint-plugin: new rule no-unsafe-type-assertion (#​10051)
  • eslint-plugin: added related-getter-setter-pairs rule (#​10192)
🩹 Fixes
  • utils: add defaultOptions to meta in rule (#​10339)
  • eslint-plugin: report deprecations used in default export (#​10330)
  • eslint-plugin: [explicit-module-boundary-types] and [explicit-function-return-type] don't report on as const satisfies (#​10315)
  • eslint-plugin: [await-thenable, return-await] don't flag awaiting unconstrained type parameter as unnecessary (#​10314)
  • eslint-plugin: [consistent-indexed-object-style] handle circular mapped types (#​10301)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.14.0

Compare Source

🚀 Features
  • eslint-plugin: [await-thenable] report unnecessary await using statements (#​10209)
  • eslint-plugin: [no-confusing-void-expression] add an option to ignore void<->void (#​10067)
🩹 Fixes
  • scope-manager: fix asserted increments not being marked as write references (#​10271)
  • eslint-plugin: [no-misused-promises] improve report loc for methods (#​10216)
  • eslint-plugin: [no-unnecessary-condition] improve error message for literal comparisons (#​10194)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

v8.13.0

Compare Source

🚀 Features
  • eslint-plugin: [only-throw-error] add allow option (#​10221)
  • eslint-plugin: [prefer-nullish-coalescing] add option ignoreBooleanCoercion (#​9924)
  • eslint-plugin: disable no-class-assign rule in eslint-recommended config (#​10250)
🩹 Fixes
  • eslint-plugin: [switch-exhaustiveness-check] add support for covering a missing property with undefined (#​10232)
  • eslint-plugin: [consistent-type-definitions] don't leave trailing parens when fixing type to interface (#​10235)
  • eslint-plugin: [no-deprecated] report when exported class implements/extends deprecated entity (#​10259)
  • eslint-plugin: [no-deprecated] report on deprecated variables used inside dynamic imports (#​10261)
  • eslint-plugin: [no-unnecessary-condition] falsey bigint should be falsey (#​10205)
❤️ Thank You

You can read about our versioning strategy and releases on our website.

eslint/eslint (eslint)

v9.16.0

Compare Source

Features

  • 8f70eb1 feat: Add ignoreComputedKeys option in sort-keys rule (#​19162) (Milos Djermanovic)

Documentation

  • 9eefc8f docs: fix typos in use-isnan (#​19190) (루밀LuMir)
  • 0c8cea8 docs: switch the order of words in no-unreachable (#​19189) (루밀LuMir)
  • 0c19417 docs: add missing backtick to no-async-promise-executor (#​19188) (루밀LuMir)
  • 8df9276 docs: add backtick in -0 in description of no-compare-neg-zero (#​19186) (루밀LuMir)
  • 7e16e3f docs: fix caseSensitive option's title of sort-keys (#​19183) (Tanuj Kanti)
  • 0c6b842 docs: fix typos in migration-guide.md (#​19180) (루밀LuMir)
  • 353266e docs: fix a typo in debug.md (#​19179) (루밀LuMir)
  • 5ff318a docs: delete unnecessary horizontal rule(---) in nodejs-api (#​19175) (루밀LuMir)
  • 576bcc5 docs: mark more rules as handled by TypeScript (#​19164) (Tanuj Kanti)
  • 742d054 docs: note that no-restricted-syntax can be used with any language (#​19148) (Milos Djermanovic)

Chores

v9.15.0

Compare Source

v9.14.0

Compare Source

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.

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

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

v4.4.3

Compare Source

Patch Changes

v4.4.2

Compare Source

Patch Changes
unjs/jiti (jiti)

v2.4.1

Compare Source

compare changes

🩹 Fixes
  • Interop modules with primitive default export (#​343)
🏡 Chore
❤️ Contributors

v2.4.0

Compare Source

compare changes

🚀 Enhancements
  • Support generic type for jiti.import<T> (#​331)
🩹 Fixes
  • Try to resolve .ts files with .js extension from js files (#​337)
🏡 Chore
🤖 CI
❤️ Contributors
nodejs/node (node)

v22.12.0

Compare Source

pnpm/pnpm (pnpm)

v9.14.4

Compare Source

v9.14.3

Compare Source

v9.14.2

Compare Source

Patch Changes

  • pnpm publish --json should work #​8788.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

v9.14.1

Compare Source

Minor Changes

  • Added support for pnpm pack --json to print packed tarball and contents in JSON format #​8765.

Patch Changes

  • pnpm exec should print a meaningful error message when no command is provided #​8752.
  • pnpm setup should remove the CLI from the target location before moving the new binary #​8173.
  • Fix ERR_PNPM_TARBALL_EXTRACT error while installing a dependency from GitHub having a slash in branch name #​7697.
  • Don't crash if the use-node-version setting is used and the system has no Node.js installed #​8769.
  • Convert settings in local .npmrc files to their correct types. For instance, child-concurrency should be a number, not a string #​5075.
  • pnpm should fail if a project requires a different package manager even if manage-package-manager-versions is set to true.
  • pnpm init should respect the --dir option #​8768.

Platinum Sponsors

Bit Bit Figma

Gold Sponsors

Discord Prisma
u|screen JetBrains
Nx CodeRabbit
Route4Me

v9.14.0

Compare Source

v9.13.2: pnpm 9.13.2

Compare Source

Patch Changes

  • Detection of circular peer dependencies should not crash with aliased dependencies #​8759. Fixes a regression introduced in the previous version.
  • Fix race condition of symlink creations caused by multiple parallel dlx processes.

Platinum Sponsors

Bit Bit 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 the dependencies Pull requests that update a dependency file label Nov 30, 2024
@coderabbitai coderabbitai
Copy link

coderabbitai bot commented Nov 30, 2024

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 5aace2f to f8a995d Compare December 3, 2024 21:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f8a995d to e5d7f46 Compare December 4, 2024 08:14
@codecov-commenter
Copy link

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 100.00%. Comparing base (8b5f307) to head (0de32d9).

Additional details and impacted files 
@@            Coverage Diff            @@
##              main      #156   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           31        31           
  Branches         4         4           
=========================================
  Hits            31        31

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@Codex- Codex- merged commit ca6bab9 into main Dec 5, 2024
5 checks passed
@Codex- Codex- deleted the renovate/all-minor-patch branch December 5, 2024 21:29
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
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@codecov-commenter @Codex-