No Matter what I do, auto import ONLY suggests dist paths...

[bradennapier]

TS Template added by @mjbvz

TypeScript Version: 4.0.0

Search Terms

• auto import
• exclude

---

Version: 1.48.0-insider
Commit: 0a7364f
Date: 2020-07-22T05:43:52.797Z
Electron: 9.1.0
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 20.0.0

Info

This is driving me loony! I can not figure out why this is happening and I have spent at least 6 hours now messing with every single setting I can find or try. I have recently moved to project references, but I do not believe this started until after - I could be wrong? How can I debug where these auto imports are from and why they are resolving here?

• It only suggests imports in the dist folder, not in the correct place while typing:

• It suggests both the correct path and the incorrect path when checking the auto fix, but it prioritizes the dist path no matter what I do:

• No matter what I do, I can not exclude dist, I have added every form of dist I can think of in the exclude path of the tsconfig.json, tsconfig.eslint.json, tsconfig.base.json, and all others that exist. I can not figure out why it is included.

• I made absolutely certain nothing ever imports from the dist folder in the src folder

tsconfig.json

{
  "files": [],
  "include": [],
  // added this recently trying to fix this, before the excludes were only at higher level
  "exclude": ["node_modules", "**/node_modules/*", "**/dist/*", "**/dist/**", "./dist"],
  "references": [
    // services
    // includes all to ./src/services/*
  ]
}

src/tsconfig.base.json

{
  // this wasnt here previously but trying to get it to exclude the dist folder
  "exclude": ["node_modules", "dist", "**/dist/*", "**/node_modules", "../dist", "../../dist"],
  "compilerOptions": {
    "allowSyntheticDefaultImports": true,
    "alwaysStrict": true,
    "baseUrl": ".",
    "composite": true,
    "declaration": true,
    "declarationMap": true,
    "downlevelIteration": true,
    "emitDecoratorMetadata": true,
    "esModuleInterop": true,
    "experimentalDecorators": true,
    "forceConsistentCasingInFileNames": true,
    "importHelpers": true,
    "lib": [
      "es2017",
      "es2018",
      "es2019"
    ],
    "module": "commonjs",
    "moduleResolution": "node",
    "newLine": "lf",
    "noImplicitAny": true,
    "noImplicitThis": true,
    "noEmitOnError": true,
    "preserveConstEnums": true,
    "removeComments": true,
    "resolveJsonModule": true,
    "strict": true,
    "strictNullChecks": false,
    "sourceMap": true,
    "target": "es2019",
    "typeRoots": ["../types", "../node_modules/@types"],
    "paths": {
      "core/*": ["./core/*"],
      "services/*": ["./services/*"]
    },
  // tried without this as well
    "plugins": [
      {
        "transform": "@zerollup/ts-transform-paths"
      }
    ]
  },
  
}

src/services/{name}/tsconfig.json

For a service, they extend the base.json

{
  "extends": "../../tsconfig.base.json",
  "include": ["./**/*.ts"],
  // tried with and without this and every variation
  "exclude": ["**/dist/**", "**/dist/*", "dist", "../../../dist/**"],
  "compilerOptions": {
    "rootDir": ".",
    "outDir": "../../../dist/services/{name}"
  },
  "references": [{ "path": "../../core" }]
}

Steps to Reproduce:

My only thought is that it somehow has to do with the fact outDir is set to dist for all of them so it generates all the dist in the dist dir?

Does this issue occur when all extensions are disabled?: Yes

[bradennapier]

Can confirm now, it appears using outDir automatically will auto import from the outDir and ignore the actual settings no matter what you do.

I have created a repro example where this is happening:

https://github.com/bradennapier/typescript-auto-import-bug

I have also tried typescript@beta as FYI

[bodinsamuel]

Same issue here, it makes references build a bit painful.

[andrewbranch]

Duplicate of #38856, although this is a better repro. Thanks for the example repo; that’s always helpful.

[typescript-bot]

This issue has been marked as a 'Duplicate' and has seen no recent activity. It has been automatically closed for house-keeping purposes.