chore(package): typescript 6 as peer optional

[furcan]

Context

First of all, great tool, thank you very much for this library.

Continuing, with the TypeScript 6 projects,
PNPM does handle this with graceful warnings but native NPM is complaining.

Note

I am also not sure why TypeScript is a peer dependency for this package, do we really need this?
Overall, this a JavaScript library and I did not see a use in lib code as TS, its JS.
But, if I am missing something, please update the PR.

---

Yes, I was missing something, its in use as an api for reading the optional tsConfig prop for madge to read/merge the given tsconfig.json for path analysis/resolution.

• https://github.com/pahen/madge/blob/master/lib/api.js#L51

And this is opening another door that, "typescript is a direct dependency" for this library by the package management aspect. The optional use case in the code itself does not make a package as peer optional.

Overall, adding TypeScript 6 as peer due to current package.json/project structure still valid, and the following comment can mitigate the issue.

• chore(package): typescript 6 as peer optional #460 (comment)

Changes

• Add TypeScript 6 as peer optional

[Milad]

Would love to see this merged.

[Jean-Dum]

Hello! Could this PR be merged?
This is one of the packages blocking the update to typescript 6, so indeed removing typescript from peer dependencies could be a great idea!

[furcan]

I tried to contact with the owner of this project, but couldn't get any answer yet (I hope they are doing well)

So, for PNPM, it handles this with graceful warnings, but for NPM, it will block the processes,

And due to unblocking your CI/CD, for NPM, you can use the following overrides config in your package.json

What is overrides?

• https://docs.npmjs.com/cli/v11/configuring-npm/package-json#overrides

Mitigation:

"overrides": {
    "madge": {
      "typescript": "$typescript",
      "precinct": {
        "detective-typescript": {
          "typescript": "$typescript"
        },
        "detective-vue2": {
          "typescript": "$typescript"
        }
      }
    }
  }