TypeScript's ecosystem of self-bundled typings does not work with npm

When npm dependencies have same packages of different versions, tsc throws duplicate identifier errors. TypeScript’s ecosystem of packages is weaker than npm, and does not have compatibility with npm. I believe this is a large problem. And this will be a popular problem because npm always install an exact version in resolving dependencies. For example, when depending a@^0.0.2 and a@^0.0.1 as another package’s dependency, its project has a@0.0.1 and a@0.0.2. npm can resolve these different versions, but TypeScript cannot.

TypeScript Version:

1.9.0-dev.20160526

[niieani]

@mhegazy What I meant is that dependencies or their dependencies might require an older, conflicting version of a given global typing (e.g. node). Will the TypeScript compiler know to distinguish the in their respectable scopes, or will it cause problems, like the OP described?

[falsandtru]

Another problem arose: #31148