When relatively importing a `.d.ts` file in a declaration file, TypeScript loads a `.ts` file instead about typescript HOT 8 OPEN

This is currently expected behavior, but I do think we should explore changing it. This happens to avoid loading your own output files as part of your input files, but it doesn’t make a lot of sense to do for files that you didn’t emit, e.g. declaration files in node_modules.

from typescript.

The .ts files are included in the published package to enable "Go to source definition" for users. Is it really necessary to place all generated files into a separate directory?

Yes. A .ts is always preferred over the .d.ts. The declaration file is considered a build artifact of the TypeScript file.

See also #56412 (comment) and #15272.

from typescript.

Also worth noting is that "Go to source definition" only works at all because the TS language service prefers to load the .ts over the .d.ts

from typescript.

I'm confused how this project even builds. The inclusion of this .ts file should have been a rootDir and/or composite violation, and we should be trying to emit a .d.ts file for it.

Can we get a sample repo?

from typescript.

If file is imported from node_modules its not considered for "rootDir" and "composite" calculations as it wont be emitted

from typescript.

I'll set up a reproduction repo tomorrow

from typescript.

Made a small reproduction, instructions are in the README: https://github.com/lucacasonato/typescript-issue-58353

from typescript.

Our workaround for this was emitting both the .js and .d.ts files into a separate directory, but this has other issues (namely import.meta.url is now wrong for users, e.g jsr-io/jsr#477).

We'll try again here, by only emitting .d.ts files into a subdirectory, and keeping the .js files next to the .ts files - I think this will work, because we can already rewrite specifiers in the .d.ts files, but it'll be weird.

from typescript.