VS Code "Jump to definition" does not work

[antoinerousseau]

Any way we can make this work again? (clicking an import to go to the definition file)

[alampros]

I think this is a typescript configuration issue. In your tsconfig.json, make sure it knows how to resolve absolute paths. For example, one of mine looks like this:

{
  "compilerOptions": {
    "baseUrl": "./src",
    "paths": {
      "*": [
        "types/*",
        "*"
      ]
    }
  },

Note: If you're not using typescript, make a jsconfig.json file instead (vscode uses typescript under the hood to infer types).

[antoinerousseau]

Thanks @alampros, this works great!
I added a jsconfig.json (since the project is unfortunately not in TS) in the project root, with this:

{
  "compilerOptions": {
    "baseUrl": "./src",
    "paths": {
      "*": ["*"]
    }
  }
}

The only details is that I now get suggestions saying

Could not find a declaration file for module 'config/constants'. '[...]/src/config/constants.js' implicitly has an 'any' type.

But nothing annoying.

[lsbyerley]

@antoinerousseau @alampros Do you know how to get rid of those suggestions? I'm using a jsconfig.json file as well and i keep seeing those suggestions when using absolute imports.

[antoinerousseau]

@lsbyerley you can turn off all VS Code TS suggestions in VS code settings if you want, but I don't know how to fix only these ones.

[alampros]

Try disabling the noImplicitAny setting. See all the compiler options here: https://www.typescriptlang.org/docs/handbook/compiler-options.html