Skip to content
This repository has been archived by the owner on Oct 12, 2022. It is now read-only.

module resolution is confused #1121

Open
chnliquan opened this issue Oct 10, 2019 · 5 comments
Open

module resolution is confused #1121

chnliquan opened this issue Oct 10, 2019 · 5 comments

Comments

@chnliquan
Copy link

In this handhook, the module resolution is that:

image

but in the real project, there is no node_modules/@types/moduleB.d.ts, it only has a node_modules/@types/moduleB directory,
image
it is confused that resolution strategy by handhook, please show the hole strategy of module resolution

@chnliquan
Copy link
Author

I think that when resolution @types/moduleB it will treat it as a folder (similar to node resolution), but I don't know which step it performed this process. I didn't explicitly according to the example.

@chnliquan
Copy link
Author

can anybody help me to solve it ?

@chnliquan
Copy link
Author

@jish @Vinnl @azu

@Vinnl
Copy link
Contributor

Vinnl commented Dec 14, 2019

I have no idea what this is about and am not familiar with the handbook @chnliquan, so I'm not sure why you tagged me...

@zhongsp
Copy link
Contributor

zhongsp commented Feb 17, 2020

The content from handbook is not that "correct". It will check /root/src/node_modules/@types/moduleB.d.ts. AND it will also check /root/src/node_modules/@types/moduleB/ directory if it contains a package.json file.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants