Error message 'Cannot find module' can be better

[ibezkrovnyi]

I'm using monorepo (no lerana, with our own scripts, doesn't matter) with 9 TypeScript projects at work.
So, I'm super excited to see "references" feature.

I was playing around with this test learn-a project, and finally was able to make it working.
Here is an developer experience issue I found:

1. Just after git clone and npm install, I see:
   
   Somehow typescript depends on /packages/pkg2/node_modules/@ryancavanaugh/pkg1 even if /packages/pkg1 exists. It is somehow counterintuitive, at least error Cannot find module '@ryancavanaugh/pkg1' can be more descriptive.

2. Just after npm install inside each /package/pkg1, /package/pkg2, /package/pkg3, I see:
   
   It is a bit surprising, because now I have both pkg1 and pkg2 inside /packages/pkg3/node_modules/@ryancavanaugh:
   
   After digging I found that pkg2@3.0.2 on npm has wrong "main" property in the package.json:

{
  "main": "index.js",
}

Should be:

{
  "main": "lib/index.js",
}

Again, error tells nothing about 'main' property of package.json.

[Izhaki]

This is messed up alright, and I've burnt a few good hours on this.

But:

• This has nothing to do with repo.
• There's some chance this has nothing to do with typescript - it's actually Node/commonJS/npm issue... it is messed up exactly the same way if you are using vanilla JS (or babel with es6 for that matter).

At any rate, I'd argue this is not the right repo for this.

Close?

[ibezkrovnyi]

Error msg still could be better, for example,

1. Cannot gind module 'pkg1' (path: /pkg2/node_modules/pkg1) - it would help a lot to resolve an issue.
2. Cannot find module 'pkg1' (cannot resolve 'main' property in package.json by path /pkg2/node_modules/pkg1) - as typescript already resolves

npm main property, and has some error message, this message could be just a bit more descriptive.
This repo was created as playground/experiments for new ts functionality, so issue was also created here. Feel free to close/move it somewhere.

[Izhaki]

I agree. Just saying this issue has nothing to do with repo.