Repository navigation
「captureRejections」property works different in node REPL with node file.js #41391
Description
Version
v15.0.1
Platform
19.5.0 Darwin Kernel Version 19.5.0
Subsystem
No response
What steps will reproduce the bug?
create a js file with the code blow
const emitter = require('events')
const em1 = new emitter({ captureRejections: true })
console.log(em1)run node file.js
output
[Symbol(kCapture)]: trueas expected.
however then i run with node REPL
output
[Symbol(kCapture)]: falsenot expected
How often does it reproduce? Is there a required condition?
always
What is the expected behavior?
captureRejections in node REPL works fine
What do you see instead?
same code
REPL output:
EventEmitter {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
[Symbol(kCapture)]: false
}node file.js output
EventEmitter {
_events: [Object: null prototype] {},
_eventsCount: 0,
_maxListeners: undefined,
[Symbol(kCapture)]: true
}Additional information
No response
Activity
[-]node REPL works different with node file.js[/-][+]「captureRejections」property works different in node REPL and node file.js[/+][-]「captureRejections」property works different in node REPL and node file.js[/-][+]「captureRejections」property works different in node REPL with node file.js[/+]Scared-Heart commentedon Jan 4, 2022
TypeStrong/ts-node#1587 (comment)
cspotcode commentedon Jan 4, 2022
This bug is triggered by
require('repl'), it does not require a REPL to be created. It is a side-effect ofrequire('repl'), which means it can reproduce without running in the REPL.domain: pass opts to `EventEmitter.init`
domain: pass opts to `EventEmitter.init`
domain: pass opts to `EventEmitter.init`
domain: pass opts to `EventEmitter.init`
domain: pass opts to `EventEmitter.init`