Clarification regarding require constraints

[martinklepsch]

NOTE: This comment on its own does nothing. But if you stick to the template, that is including the fs module exactly the same way naming it also "fs", the compiler will know how to handle the module and its subcomponents. For example:

// This is bad:
var EventEmitter = require("events").EventEmitter;

// This is good:
var events = require("events");
var EventEmitter = events.EventEmitter;

The description and the example don't fully match up for me. I just tried compiling something with

var f = require("fs")
var cp = require("child_process")

and it worked fine. Is that what's expected?

Also thank you for this project!

[dcodeIO]

This only matters when compiling with advanced optimizations, isn't an issue otherwise.

[martinklepsch]

@dcodeIO Sure. I forgot to say that I compiled with advanced optimizations. :)

[dcodeIO]

Ah, ok. Iirc the Closure Compiler team has also added node externs to the compiler, partly based on this package here, so it might be that.

[martinklepsch]

Oh, that's cool. That said do you know any points of reference for properly writing externs for node modules? I don't quit understand how it deals with the fact that things can be imported under different names...