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

tsconfig.json "references" is not evaluated #94

Open
DrJume opened this issue Mar 1, 2022 · 6 comments
Open

tsconfig.json "references" is not evaluated #94

DrJume opened this issue Mar 1, 2022 · 6 comments

Comments

@DrJume
Copy link

DrJume commented Mar 1, 2022

When reading tsconfig.json, it seems to be ignoring the "references" array which includes paths to other tsconfig files in the same directory.

You can reproduce my repo with npm init vue@3 and then add eslint-plugin-import with this resolver.

@JounQin
Copy link
Collaborator

JounQin commented Mar 1, 2022

Yep, references is not supported yet, and PR welcome to add notice about it or implement this feature.

@DrJume
Copy link
Author

DrJume commented Mar 1, 2022

My workaround was to include the referenced tsconfigs in the .eslintrc.js with:

module.exports = {
  // ...,
  settings: {
    'import/resolver': {
      typescript: {
        project: [
          __dirname + '/tsconfig.json',
          __dirname + '/tsconfig.other.json',
        ],
      },
    },
  },
}

line0 added a commit to line0/eslint-import-resolver-typescript that referenced this issue Jul 6, 2022
…terns

`getTsConfig` treats every path as a directory and looks for a `tsconfig.json` in the closest parent directory

this breaks any configuration that uses file names other than tsconfig.json, as is convention for [solution-style](https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig) tsconfigs, which is exacerbated by the lack of support for the `references` field (see import-js#94)
line0 added a commit to line0/eslint-import-resolver-typescript that referenced this issue Jul 6, 2022
…terns

`getTsConfig` treats every path as a directory and looks for a `tsconfig.json` in the closest parent directory

this breaks any configuration that uses file names other than tsconfig.json, as is convention for [solution-style](https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig) tsconfigs, which is exacerbated by the lack of support for the `references` field (see import-js#94)
line0 added a commit to line0/eslint-import-resolver-typescript that referenced this issue Jul 6, 2022
…terns

`getTsConfig` treats every path as a directory and looks for a `tsconfig.json` in the closest parent directory

this breaks any configuration that uses file names other than tsconfig.json, as is convention for [solution-style](https://devblogs.microsoft.com/typescript/announcing-typescript-3-9/#solution-style-tsconfig) tsconfigs, which is exacerbated by the lack of support for the `references` field (see import-js#94)
@psibean
Copy link

psibean commented Oct 11, 2022

My workaround was to include the referenced tsconfigs in the .eslintrc.js with:

module.exports = {
  // ...,
  settings: {
    'import/resolver': {
      typescript: {
        project: [
          __dirname + '/tsconfig.json',
          __dirname + '/tsconfig.other.json',
        ],
      },
    },
  },
}

This didn't seem to solve the problem for me. Any paths defined that are pointing to a reference still don't seem to work, but they work fine if I update their imports to use a relative path instead. Is it possible to see more of your config, or a sample repo?

Would highly appreciate!

@JounQin
Copy link
Collaborator

JounQin commented Oct 11, 2022

This didn't seem to solve the problem for me. Any paths defined that are pointing to a reference still don't seem to work, but they work fine if I update their imports to use a relative path instead. Is it possible to see more of your config, or a sample repo?

Or maybe you can provide a reproduction instead.

@psibean
Copy link

psibean commented Oct 11, 2022

This didn't seem to solve the problem for me. Any paths defined that are pointing to a reference still don't seem to work, but they work fine if I update their imports to use a relative path instead. Is it possible to see more of your config, or a sample repo?

Or maybe you can provide a reproduction instead.

Good point!

I should, given I'm the one with the issue, that is on me. I can't put together a full reproduction right now, but here's a breakdown of my config files.

I have a single root tsconfig.json which is only used for linting:

{
  "compilerOptions": {
    "module": "ESNext",
    "target": "es2020",
    "esModuleInterop": true,
    "noImplicitAny": true,
    "moduleResolution": "node",
    "sourceMap": false,
    "baseUrl": ".",
    "strictNullChecks": true,
    "isolatedModules": false,
    "composite": true,
    "removeComments": true,
    "allowSyntheticDefaultImports": true,
    "paths": {
      "@backend/*": ["./backend/src/*"],
      "@client/*": ["./frontend/src"],
      "@app/*": ["./backend/src/app/*"],
      "@shared-types": ["./shared-types/src/*"],
      "*": ["frontend/node_modules/*", "backend/node_modules/*"],
    },
  },
  "include": [
    "./frontend",
    "./backend",
    "./shared-types"
  ],
}

These paths are replicated in ./backend/tsconfig.json, ./frontend/tsconfig.json, and ./shared-types/tsconfig.json.

And my .eslintrc.cjs looks like this:

module.exports = {
  extends: [
    'eslint:recommended',
  ],
  env: {
    browser: true,
    node: true,
  },
  root: true,
  ignorePatterns: [
    ".*",
    "lib/**/*",
  ],
  parserOptions: {
    sourceType: "module",
    ecmaVersion: 2020
  },
  overrides: [
    {
      files: ["**/*.ts"],
      extends: [
        'eslint:recommended',
        'plugin:@typescript-eslint/recommended',
        'plugin:@typescript-eslint/recommended-requiring-type-checking',
      ],
      parser: '@typescript-eslint/parser',
      parserOptions: {
        tsconfigRootDir: __dirname,
        project: [
          './tsconfig.json',
        ],
        EXPERIMENTAL_useSourceOfProjectReferenceRedirect: true
      },
      plugins: ['@typescript-eslint', 'import'],
      settings: {
        "import/parsers": {
          "@typescript-eslint/parser": [".ts", ".tsx"]
        },
        "import/resolver": {
          "typescript": {
            "project": [
              "tsconfig.json",
              __dirname + "/shared-types/tsconfig.json",
              __dirname + "/backend/tsconfig.json",
              __dirname + "/frontend/tsconfig.json"
            ]
          }
        }
      }
    }
  ]
};

@JounQin
Copy link
Collaborator

JounQin commented Oct 11, 2022

@psibean Thanks, but you need to provide a minimal but runnable reproduction so that we can help to debug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants