Dependency analysis

Currently it is very hard to analyze where a dependency will be imported, for example:

type t

@module("dep") external make: unit => t = "make"

let timeMake = () => {
  Js.Console.timeStart("make")
  let t = make()
  Js.Console.timeEnd("make")
  t
} 

A consuming module may import dep directly, or it may not depending on which function is used and if there is an interface file.

If dependencies, devDependencies, and peerDependencies are not properly set this may become a problem for certain package manager setups. A small change could end up causing a runtime error. It could be particularly insidious if it is a rarely used or lazy loaded binding.

Due to the different dependency types often being misunderstood and the complexity of analysis, I believe ReScript should have the ability to check package.json dependencies for correctness.

I've had Claude create an example project here that failures when using pnpm style linking. The main branch uses ReScript 12 and ESM, but there is also a rescript-11-cjs branch for reference.

BTW it could be helpful if this feature was implemented in a way that we could integrate with Knip as a plugin

Inizia con l'esempio collegato res-dep-issue, confronta i suoi branch main e rescript-11-cjs e riproduci il problema di linking in stile pnpm. Poi leggi gli entry point dell'analisi delle dipendenze del compilatore e determina come dovrebbero essere verificate le dipendenze di package.json. Il lavoro è completato quando l'analisi proposta identifica in modo affidabile le dipendenze errate e offre un percorso chiaro per l'integrazione con Knip.