Skip to content
This repository has been archived by the owner on Apr 30, 2019. It is now read-only.

Legacy Typings Behavior #222

Open
gravidThoughts opened this issue Sep 23, 2015 · 0 comments
Open

Legacy Typings Behavior #222

gravidThoughts opened this issue Sep 23, 2015 · 0 comments

Comments

@gravidThoughts
Copy link

I am confused by the semantics of legacy typings behavior of tsd.

In bower, bower install angular@1.3.8 installs 1.3.8, but the version is not coupled to the bower_components directory structure, nore the source javascript. The coupling to the version occurs in bower.json.

When I execute bower install angular, it replaces 1.3.8 with the latest version of angular. All of the build automation continues to work properly because it does not depend on bower.json. It depends on the angular source always being bower_components\angular\angular.js.

Tsd appears to treat this improperly.

tsd install angular -v "1.2.0" -rso to incorporate this tool into a legacy system. Months later, tsd install angular. Now everything is broken because of duplicate declarations.

Am I missing something? Why does tsd not simply use typings\\<bundle>\\*.d.ts as the structure for all files regardless of version? What is the practical purpose of being able to install 3 versions of angular.d.ts?

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

1 participant