I'm using Underscore.js in my project. Almost all files have this line of code: var _ = require('underscore')
.
The require
function is synchronous so the same file is loaded each time it is used. Is this the right thing to do? Doesn't this affect performance?
Instead of this, is it okay to define a global variable in the app.js
file?
_ = require('underscore')
I've read that you shouldn't use global variables, but this seems to be a valid use case.
In the end requiring that module in a function vs at the top of a module consumes the same amount of memory, but requiring at the top of a module means it will always be ready to go when someone requests that route and you would instead factor that extra 30 minuets into your deployment time, not at 3am in the morning ...
If the module, once evaluated, is imported again, it's second evaluation is skipped and the resolved already exports are used. If a module is imported multiple times, but with the same specifier (i.e. path), the JavaScript specification guarantees that you'll receive the same module instance.
From the node.js documentation:
Modules are cached after the first time they are loaded. This means (among other things) that every call to require('foo') will get exactly the same object returned, if it would resolve to the same file.
Multiple calls to require('foo') may not cause the module code to be executed multiple times. This is an important feature. With it, "partially done" objects can be returned, thus allowing transitive dependencies to be loaded even when they would cause cycles.
So multiple calls to requiring underscore
will not affect the performance as it will be loading a cached version of the module.
Source: https://nodejs.org/api/modules.html
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With