diff options
author | Anna Henningsen <anna@addaleax.net> | 2019-10-11 18:38:50 +0200 |
---|---|---|
committer | Anna Henningsen <anna@addaleax.net> | 2019-11-01 19:58:41 +0100 |
commit | d7452b7140929835f4032099106fc9d14e668210 (patch) | |
tree | f88c8d672046e923f2a2071a6fe88a40f53bff0c /src | |
parent | fc02cf586a4b146195a5f09a21fb34269657c484 (diff) | |
download | android-node-v8-d7452b7140929835f4032099106fc9d14e668210.tar.gz android-node-v8-d7452b7140929835f4032099106fc9d14e668210.tar.bz2 android-node-v8-d7452b7140929835f4032099106fc9d14e668210.zip |
module: warn on using unfinished circular dependency
Warn when a non-existent property of an unfinished module.exports
object is being accessed, as that very often indicates the presence
of a hard-to-detect and hard-to-debug problem.
This mechanism is only used if `module.exports` is still a
regular object at the point at which the second, circular `require()`
happens.
The downside is that, temporarily, `module.exports` will have a
prototype other than `Object.prototype`, and that there may
be valid uses of accessing non-existent properties of unfinished
`module.exports` objects.
Performance of circular require calls in general is not
noticeably impacted.
confidence improvement accuracy (*) (**) (***)
module/module-loader-circular.js n=10000 3.96 % ±5.12% ±6.82% ±8.89%
Example:
$ cat a.js
'use strict';
const b = require('./b.js');
exports.fn = () => {};
$ cat b.js
'use strict';
const a = require('./a.js');
a.fn();
$ node a.js
(node:1617) Warning: Accessing non-existent property 'fn' of module exports inside circular dependency
/tmp/b.js:4
a.fn();
^
TypeError: a.fn is not a function
at Object.<anonymous> (/tmp/b.js:4:3)
[...]
PR-URL: https://github.com/nodejs/node/pull/29935
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Diffstat (limited to 'src')
0 files changed, 0 insertions, 0 deletions