index.ts

import monorepoDepLocation from './src/rules/monorepo-dep-location';

// Vite doesn't include `require.resolve` in the module graph, so import these
// to make sure they get built
import './src/configs/javascript';
import './src/configs/nx-javascript';
import './src/configs/nx-typescript';
import './src/configs/typescript';
import './src/configs/vue3-javascript';
import './src/configs/vue3-typescript';
import './src/configs/base/extraneous-deps';
import './src/configs/base/javascript';
import './src/configs/base/nx';
import './src/configs/base/typescript';
import './src/configs/base/vue';

export default {
  configs: {
    // Why are we doing this instead of importing directly? When running eslint through the vs code
    // eslint plugin, a single node process repeatedly creates new instances of eslint.
    // configs/base/extraneous-deps evaluates different results based on the cwd eslint is run from.
    // When using extends with require.resolve, eslint will use import-fresh to include configs
    // bypassing node's module cache. However, when a plugin is loaded, it is NOT loaded bypassing
    // the module cache. So this makes sure that when the vs code plugin lints files in different
    // directories, it will use a correctly-generated config, rather than a "stale" config generated
    // for a different directory.
    javascript: { extends: require.resolve('./src/configs/javascript') },
    'nx-javascript': { extends: require.resolve('./src/configs/nx-javascript') },
    'nx-typescript': { extends: require.resolve('./src/configs/nx-typescript') },
    typescript: { extends: require.resolve('./src/configs/typescript') },
    'vue3-javascript': { extends: require.resolve('./src/configs/vue3-javascript') },
    'vue3-typescript': { extends: require.resolve('./src/configs/vue3-typescript') },
  },
  rules: {
    'monorepo-dep-location': monorepoDepLocation,
  },
};