Module resolution issue with project reference

[jsbravoc]

Description

• I use svelte-check with a custom --tsconfig path. However, the VSCode extension uses the default one (tsconfig.json)

Proposed solution

Add an extension configuration to set the tsconfig path.

"svelte.plugin.typescript.tsconfigPath": "./tsconfig.json"

Alternatives

No response

Additional Information, eg. Screenshots

No response

[jasonlyu123]

This has been proposed in TypeScript before but was rejected(microsoft/vscode#12463, microsoft/TypeScript#11224). While the tsconfig searching in svelte-language-server is currently not entirely controlled by TypeScript, it is better to stay consistent with TypeScript as It'll introduce inconsistencies between js/ts files and svelte files. Can you share why you can't use tsconfig.json? Alternatively, you can create multiple tsconfig in different directories with different include configs. Or use a solution style tsconfig to reference a tsconfig with a name other than "tsconfig.json".

[jsbravoc]

Can you share why you can't use tsconfig.json?

I’m encountering issues with TypeScript imports when using project references. If I remove the project references, everything works correctly.

Here's a minimal reproducible example: https://github.com/jsbravoc/min-repo-svelte-ts

In this setup, there are two TSConfigs:

• One includes the project references.

• Another extends the first but removes the references.

In CI, I'm using the second TSConfig, and I’d like the VSCode extension to use it as well.

---

Edit: I want to keep the TSConfig with project references because I'm using Nx with the TypeScript plugin. This plugin automatically updates all TSConfig files in the monorepo and sets project references based on package dependencies https://nx.dev/nx-api/js/generators/typescript-sync

[jasonlyu123]

The import issue is a bug so I'll fix it instead.