Config object order matter when using with eslint-plugin-tailwindcss?

[Soundvessel]

More of a curious question... When using with other plugins, like eslint-plugin-tailwindcss, that lint the same file types, does the order of config objects matter?

For example here are my config objects:

  // CSS
  {
    name: 'Project/css',
    files: ['**/*.css'],
    plugins: {
      css: pluginCss,
    },
    extends: ['css/recommended'],
    language: 'css/css',
    languageOptions: {
      customSyntax: tailwindSyntax,
    },
    rules: {
      // TODO: investigate fixes inc use of @support
      'css/use-baseline': 'off',
    },
  },

  // Tailwind
  {
    name: 'Project/Tailwind',
    plugins: {
      tailwindcss: pluginTailwindcss,
    },
    extends: ['tailwindcss/recommended'],
    rules: {
      'tailwindcss/no-custom-classname': [
        'warn',
        {
          whitelist: ['card', 'pi', '^((p-|pi-|sx__).*)'],
        },
      ],
    },
  },

[nzakas]

Sorry, this question is too abstract to answer accurately. If you've run into a problem with the above code, please describe the problem.