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.

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

fix(deps): update all non-major dependencies #200

Merged
merged 1 commit into from
Dec 22, 2024
Merged

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Nov 25, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@remix-run/css-bundle (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/dev (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/express (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/node (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/react (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/serve (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@remix-run/server-runtime (source) 2.15.0 -> 2.15.1 age adoption passing confidence
@vercel/remix (source) 2.15.0 -> 2.15.1 age adoption passing confidence
eslint (source) 9.15.0 -> 9.17.0 age adoption passing confidence
eslint-plugin-import-x 4.4.2 -> 4.6.1 age adoption passing confidence
eslint-plugin-react-hooks (source) 5.1.0-rc-fb9a90fa48-20240614 -> 5.1.0 age adoption passing confidence
globals 15.12.0 -> 15.14.0 age adoption passing confidence
lucide-react (source) ^0.460.0 -> ^0.468.0 age adoption passing confidence
pnpm (source) 9.13.2 -> 9.15.0 age adoption passing confidence
typescript-eslint (source) 8.15.0 -> 8.18.1 age adoption passing confidence

Release Notes

remix-run/remix (@​remix-run/css-bundle)

v2.15.1

Compare Source

remix-run/remix (@​remix-run/dev)

v2.15.1

Compare Source

Patch Changes
remix-run/remix (@​remix-run/express)

v2.15.1

Compare Source

Patch Changes
remix-run/remix (@​remix-run/node)

v2.15.1

Compare Source

Patch Changes
remix-run/remix (@​remix-run/react)

v2.15.1

Compare Source

Patch Changes
remix-run/remix (@​remix-run/serve)

v2.15.1

Compare Source

Patch Changes
remix-run/remix (@​remix-run/server-runtime)

v2.15.1

Compare Source

vercel/remix (@​vercel/remix)

v2.15.1

Date: 2024-12-09

Patch Changes
  • create-remix - Move fs-extra from devDependencies to dependencies (#​10300)

Full Changelog: v2.15.0...v2.15.1

eslint/eslint (eslint)

v9.17.0

Compare Source

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

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

v4.4.3

Compare Source

Patch Changes
facebook/react (eslint-plugin-react-hooks)

v5.1.0

Compare Source

sindresorhus/globals (globals)

v15.14.0

Compare Source

v15.13.0

Compare Source

lucide-icons/lucide (lucide-react)

v0.468.0: New icons 0.468.0

Compare Source

New icons 🎨

v0.467.0: New icons 0.467.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.466.0: New icons 0.466.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.465.0: New icons 0.465.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.464.0: New icons 0.464.0

Compare Source

Modified Icons 🔨

v0.463.0: New icons 0.463.0

Compare Source

Modified Icons 🔨

v0.462.0: New icons 0.462.0

Compare Source

New icons 🎨

Modified Icons 🔨

v0.461.0: New icons 0.461.0

Compare Source

New icons 🎨

Modified Icons 🔨

pnpm/pnpm (pnpm)

v9.15.0

Compare Source

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

typescript-eslint/typescript-eslint (typescript-eslint)

v8.18.1

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

v8.18.0

Compare Source

🩹 Fixes
❤️ Thank You
  • rtritto

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

v8.17.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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

v8.16.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

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


Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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.

Copy link

vercel bot commented Nov 25, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
remix-gospel-stack-nextjs-app ✅ Ready (Inspect) Visit Preview 💬 Add feedback Dec 22, 2024 0:49am

@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 5bb877e to 49c1fe3 Compare November 28, 2024 19:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 49c1fe3 to 43fc275 Compare November 30, 2024 09:59
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 43fc275 to f21eaaa Compare December 1, 2024 18:29
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f21eaaa to 19c2413 Compare December 2, 2024 12:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 19c2413 to 3b42ca2 Compare December 2, 2024 21:47
@renovate renovate bot changed the title fix(deps): update all non-major dependencies chore(deps): update all non-major dependencies Dec 2, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 3b42ca2 to 658c610 Compare December 4, 2024 20:07
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 658c610 to 7c0c6a7 Compare December 5, 2024 19:37
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 7c0c6a7 to 4d8a48a Compare December 6, 2024 08:25
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4d8a48a to eb9e256 Compare December 6, 2024 11:47
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from eb9e256 to f2e68e4 Compare December 6, 2024 12:54
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f2e68e4 to 0b2d22e Compare December 7, 2024 11:14
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 0b2d22e to f50b11c Compare December 8, 2024 10:15
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from f50b11c to 10b1ff1 Compare December 8, 2024 13:18
@renovate renovate bot changed the title chore(deps): update all non-major dependencies chore(deps): update all non-major dependencies - autoclosed Dec 8, 2024
@renovate renovate bot closed this Dec 8, 2024
@renovate renovate bot deleted the renovate/all-minor-patch branch December 8, 2024 18:32
@renovate renovate bot changed the title chore(deps): update all non-major dependencies - autoclosed chore(deps): update all non-major dependencies Dec 9, 2024
@renovate renovate bot reopened this Dec 9, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from 10b1ff1 to 4151fb7 Compare December 9, 2024 03:19
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 4151fb7 to 9e29532 Compare December 9, 2024 16:53
@renovate renovate bot changed the title chore(deps): update all non-major dependencies fix(deps): update all non-major dependencies Dec 10, 2024
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 9e29532 to 94f73de Compare December 12, 2024 17:41
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 94f73de to 052b585 Compare December 16, 2024 22:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 052b585 to cac91c7 Compare December 19, 2024 17:48
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from cac91c7 to 1b18e41 Compare December 20, 2024 14:57
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 1b18e41 to 29c005c Compare December 21, 2024 16:36
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 29c005c to 53ce5fe Compare December 22, 2024 07:31
@renovate renovate bot force-pushed the renovate/all-minor-patch branch from 53ce5fe to 351a611 Compare December 22, 2024 12:48
@PhilDL PhilDL merged commit 36aca13 into main Dec 22, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant