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

Does tsd link not work? #130

Open
jeremymwells opened this issue Mar 13, 2015 · 4 comments
Open

Does tsd link not work? #130

jeremymwells opened this issue Mar 13, 2015 · 4 comments

Comments

@jeremymwells
Copy link

I run tsd link and get the standard help output. I get the same output when I run tsd foo.

@cybrown
Copy link

cybrown commented Mar 15, 2015

the link command works from version 0.6 which is on the dev/next branch, the version on npm is 0.5.7

@azu
Copy link

azu commented Apr 9, 2015

I noticed that tsd link could't handle Scoped packages.

I installed @myorg/mypackage, then the scoped packages is installed under the @myorg directory.

node_modules
├── @myorg
│   └── mypackage
│       └── package.json
├── browserify
│   └──package.json
├── del
│   ├── index.js
│   └──package.json
....

tsd(dev/next) seem seek pacakge.json which is just below node_modules/*.

As a result, tsd link not work for @myorg/mypackage. 💭

@blakeembrey
Copy link
Member

Hi @jeremymwells, did install tsd@next help you?

@azu Thanks for the report, I'm definitely going to make sure it's supported going forward. Support local dependencies is going to be a priority for me 😄

@blakeembrey blakeembrey mentioned this issue May 1, 2015
7 tasks
@pleerock
Copy link

+1 what what @azu is talking about

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

5 participants