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

Support non-Github repos. #135

Open
bradleyayers opened this issue Mar 26, 2015 · 5 comments
Open

Support non-Github repos. #135

bradleyayers opened this issue Mar 26, 2015 · 5 comments

Comments

@bradleyayers
Copy link

I want to use tsd with a non-Github server, but tsd is opinionated at the moment about Github. It looks like it makes assumptions about the shape of the REST API, and expects the repo attribute in tsd.json to be the format <owner>/<repo>.

It would be good to be able to use tsd with an internal Git repo.

@madaz
Copy link

madaz commented Apr 28, 2015

👍 Required for internal legacy library definitions

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

👍 This is definitely critical for internal definitions.

@httpete
Copy link

httpete commented Dec 14, 2015

any update on this? We have a secure dome environment, and what I want to do is point tsd to our internally mirrored DefinitelyTyped github repo just like I can with bower and npm.

@blakeembrey
Copy link
Member

I'm available to review a PR for this feature. I don't know what "mirrored DefinitelyTyped github repo" means though, maybe you're interested in #223? If you're interested in installing from arbitrary locations, maybe you want something more like http://github.com/typings/typings.

@daudt
Copy link

daudt commented Jan 5, 2016

Any idea when the next npm release will be? I'm really in need of this particular feature.

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

6 participants