• it assigns to the exports variable to export one people program

Not anymore: dependencies have to be clearly declared, and finding a bit of rule just suggests studying the document route when you look at the need declaration

Is not that during the worldwide range? No, there’s no global range here. Each module features its own scope. It is like creating each component implicitly covered with a anonymous work (consequently factors explained tend to be local towards component).

OK, think about calling for jQuery or other library? There are basically two methods to need a document: either by indicating a file course (like ./lib/model.js ) or by demanding it by-name: var $ = require(‚jquery‘); . Items necessary for document road are situated immediately by their own title in the file program. Points necessary for title are „packages“ and so are searched of the need system. In the example of Node, they makes use of an easy directory browse; in the browser, well, we can define bindings as you will discover later.

Is not this the same as merely covering all things in a closing, that you might currently do? No, not by a long try.

It doesn’t unintentionally adjust global state, and it just exports the one thing. Each CommonJS component executes within the very own performance framework. Factors is local towards the component, not worldwide. Possible best export one object per component.Continue reading→