New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does `tsd link` not work? #130

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

Comments

Projects
None yet
5 participants
@jeremymwells
Copy link

jeremymwells commented Mar 13, 2015

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

@cybrown

This comment has been minimized.

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

This comment has been minimized.

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

This comment has been minimized.

Copy link
Member

blakeembrey commented Apr 29, 2015

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 referenced this issue May 1, 2015

Closed

TSD Future #150

7 of 7 tasks complete
@pleerock

This comment has been minimized.

Copy link

pleerock commented Oct 15, 2015

+1 what what @azu is talking about

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment