import inconsistent? #11025

Activity

1. Ryan Cavanaugh (RyanCavanaugh)

   added

   QuestionAn issue which isn't directly actionable in codeAn issue which isn't directly actionable in code

   on Sep 21, 2016
2. RyanCavanaugh commented on Sep 21, 2016

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Sep 21, 2016

   Member

   More actions

   import "http2"
   

   This is what we generally call a "forced" import. It doesn't create a local binding, so there's no reason to force it to resolve to a known module. These are usually used to load non-code resources anyway.

   import http2 from "http2"
   

   There's no definition for the "http2", so we don't know how to resolve the type of the local http2 binding

   var http2 = require("http2");

   This is using the underlying module loader.

   You can write this to get the behavior you want

   import _http = require('http'); // don't use _http in any other place
   var http2 = <typeof _http>require('http2');
3. BobFrankston commented on Sep 21, 2016

   

   Bob Frankston (BobFrankston)

   on Sep 21, 2016

   Author

   More actions

   Thanks very much.
4. Bob Frankston (BobFrankston)

   closed this as completedon Sep 21, 2016
5. BobFrankston commented on Sep 21, 2016

   

   Bob Frankston (BobFrankston)

   on Sep 21, 2016

   Author

   More actions

   Reopening this. First, the <typeof ..> notation is not at all obvious until you see it. Thanks.

   But now in using "http.

   import http1 = require("http");
   var http = <typeof http1>require("http2");
      ServerResponder(req: http.ServerRequest, response: http.ServerResponse) {
   
   Error   TS2503  Cannot find namespace 'http'.
   
   

   same for "var http2 = ..."
6. Bob Frankston (BobFrankston)

   reopened this on Sep 21, 2016
7. RyanCavanaugh commented on Sep 21, 2016

   

   Ryan Cavanaugh (RyanCavanaugh)

   on Sep 21, 2016

   Last edited by RyanCavanaugh

   Member

   More actions

   Sorry this is a bit confusing -- you'll want to use http1 in namespace positions (places where a dotted name produces a type), e.g. http1.ServerRequest. #10187 would create a way to do this unconfusingly by letting you alias the namespace side of http1.
8. BobFrankston commented on Sep 21, 2016

   

   Bob Frankston (BobFrankston)

   on Sep 21, 2016

   Last edited by BobFrankston

   Author

   More actions

   Thanks. Yeah -- getting to the truth by lying. I'll have to take the time go through the aliasing procedure given the overlapping mechanisms. And, more generally,how to get the declarations for importing JavaScript but that's probably best for the suggestions forum.
9. Bob Frankston (BobFrankston)

   closed this as completedon Sep 21, 2016
10. BobFrankston commented on Sep 22, 2016

    

    Bob Frankston (BobFrankston)

    on Sep 22, 2016

    Author

    More actions

    OK, gets stranger. Turns out that https://github.com/molnarg/node-http2 has an index.d.ts file and even mentions Typescript 1.8 compatibility. ! But it's unclear how to use it. My gut feel is that it should be found automatically. So I explicitly added

    /// <reference path="./node_modules\http2\typings\globals\node\index.d.ts" />
    

    which generates declaration errors.

    I feel this is close but so far.
11. Bob Frankston (BobFrankston)

    reopened this on Sep 22, 2016
12. Mohamed Hegazy (mhegazy)

    closed this as completedon Apr 21, 2017
13. microsoft

    locked and limited conversation to collaborators on Jun 19, 2018