TypeScript fails to resolve dependency in monorepo given specific conditions about typescript HOT 5 OPEN

It looks like you're using a package manager that doesn't set up symlinks, so TS has no way to know that you have the outer monorepo setup, thus doesn't have any way to know that packages/ is where you can find a. The easiest way is to address that is to just add a baseUrl:

    "baseUrl": "../"

from typescript.

I see I forgot to specify you have to run npm install, but I did do this in my testing. This creates symlinks.

I forgot that TypeScript doesn’t validate bare import specifiers, but it does check dynamic imports. Apart from that the difference between an import statement or an import declaration doesn’t matter. I updated the example repo to make b export something from a. This also makes the error appear.

This made me suspicious, because in my real world code one workspace does have this problem, but another doesn’t. It turns out enabling resolveJsonModule in the dependant module (b) makes the error go away, even though there are no JSON imports anywhere. I added a this option, commented, so it can be toggled easily.

baseUrl doesn’t solve the problem, because the real world example uses scoped packages. This can be solved using paths, but I don’t think that should be necessary.

from typescript.

Something's gone wrong here; tsc -b -f b fails but tsc -p b does not

from typescript.

Apparently the workaround of enabling resolveJsonModule only works if this is enabled in the configuration file of b directly, not if it’s enabled in a configuration it extends from.

from typescript.

Apparently the workaround of enabling resolveJsonModule only works if this is enabled in the configuration file of b directly, not if it’s enabled in a configuration it extends from.

That sounds like a bug - if you can repro it, you should report that in a separate issue.

from typescript.