call of method get Unknown global name. But why ?

[ghost]

This is the code:

 var req = https.get(request, function(res) {
      res.setEncoding('utf8');

and this is the declaration

declare module "https" {
    declare function get(config: https$Config, callback: (res: https$Response) => void): https$Request;
}

This gives me "call of method get Unknown global name". But why ?

[garetht]

I'm also getting this, and as far as I can tell it seems to occur with Node module names. In this simplified example requiring https and declaring the module https produces the error, changing both to fs or stream produces the error, but changing it to a non-core Node module name does not.

Code

var M = require("https");
M.foo()

Declaration

declare module https {
  declare function foo(): void;
}

Output

.js:3:1,7: call of method foo
Unknown global name

[garetht]

This probably has to do with the interaction of the core library definitions and the user's. The error seems to arise because the https and other node declarations have not yet been implemented in the core library. I downloaded and built the latest version of flow and ran it with the --no-flowlib option, which removed the error.

I think the bug here might be unexpected behavior when two or more declaration blocks for the same module are present. I would expect one of them to override the other, rather than each being considered as a separate block.

[ghost]

Thank you for reporting this issue and appreciate your patience. We've notified the core team for an update on this issue. We're looking for a response within the next 30 days or the issue may be closed.

[gabelevi]

We are planning to introduce some way to override declarations eventually. Let's use #396 to track that.