fix: remove SIGWINCH listener upon closing the REPL

lib/node_modules/@stdlib/repl/lib/main.js

@@ -274,7 +274,7 @@
 	setNonEnumerableReadOnly( this, '_ttyWrite', this._rli._ttyWrite );
 
 	// Overwrite the private `ttyWrite` method to allow processing input before a "keypress" event is triggered:
 	this._rli._ttyWrite = beforeKeypress; // WARNING: overwriting a private property
 
 	// Add event listeners:
 	this._rli.on( 'close', onClose );
@@ -294,9 +294,9 @@
 	// Write a welcome message:
 	this._wstream.write( opts.welcome );
 
 	// TODO: check whether to synchronously initialize a REPL history file
 
 	// TODO: check whether to synchronously initialize a REPL log file
 
 	// Check whether to load and execute a JavaScript file (e.g., prior REPL history) upon startup...
 	if ( opts.load ) {
@@ -370,6 +370,7 @@
 
 		debug( 'Readline interface closed.' );
 		self._istream.removeListener( 'keypress', onKeypress );
+		proc.removeListener( 'SIGWINCH', onSIGWINCH );
 
 		debug( 'Exiting REPL...' );
 		self.emit( 'exit' );
@@ -444,9 +445,9 @@
 		// Update the internal command history buffer: [..., <id>, <cmd>, <success>, ...]
 		self._history.push( self._count, cmd, success );
 
 		// TODO: if successful and if necessary, (asynchronously?) write the command to a history file (question: do we only want to write successful commands to the history file? maybe we need to option for limiting to successful commands?)
 
 		// TODO: if necessary, (asynchronously?) write the command and result to a log file (JSON serialization?)
 	}
 }
 
@@ -670,7 +671,7 @@
 
 	// Before creating a new execution context in a non-sandboxed environment, remove current workspace variables in order to allow garbage collection and avoid memory leaks (e.g., variables/functions declared during a REPL session which might remain bound to the environment `global` after clearing a REPL):
 	if ( this._sandbox === false ) {
 		// WARNING: in a non-sandboxed environment, if a global variable is externally introduced during a REPL session (i.e., introduced via a mechanism outside of the REPL environment), we will delete that global variable, which means the following logic may introduce unintended side-effects for this particular edge case (e.g., application code may expect the presence of the subsequently deleted global variable). While not ideal, (a) user applications should not be introducing globals to begin with and (b) the probability of a user running a REPL session, a user clearing that REPL session, AND a global variable being introduced between starting a REPL and clearing the REPL should be negligible.
 		tmp = this._context.vars();
 		for ( i = 0; i < tmp.length; i++ ) {
 			if ( isConfigurableProperty( this._context, tmp[ i ] ) ) {
@@ -1063,9 +1064,9 @@
 	// Clear the command queue:
 	this._queue.clear();
 
 	// TODO: ensure REPL history is saved (flushed) to file before closing the REPL (see https://github.com/nodejs/node/blob/b21e7c7bcf23a2715951e4cd96180e4dbf1dcd4d/lib/repl.js#L805)
 
 	// TODO: ensure REPL log is saved (flushed) to file before closing the REPL
 
 	nextTick( onTick );
 
@@ -1088,7 +1089,7 @@
 
 		// If this is a non-sandboxed REPL, remove global variables/properties which were introduced during context creation and by a user during a REPL session...
 		if ( self._sandbox === false ) {
 			// WARNING: in a non-sandboxed environment, if a global variable is externally introduced during a REPL session (i.e., introduced via a mechanism outside of the REPL environment), we will delete that global variable, which means the following logic may introduce unintended side-effects for this particular edge case (e.g., application code may expect the presence of the subsequently deleted global variable). While not ideal, (a) user applications should not be introducing globals to begin with and (b) the probability of a user running a REPL session, a user closing that REPL session, AND a global variable being introduced between starting a REPL and closing the REPL should be negligible.
 			tmp = self._context.vars(); // current workspace variables
 			for ( i = 0; i < tmp.length; i++ ) {
 				if ( isConfigurableProperty( self._context, tmp[ i ] ) ) {
@@ -1168,7 +1169,7 @@
 		throw new Error( format( 'invalid argument. First argument must be a recognized setting. Value: `%s`.', name ) );
 	}
 	if ( nargs === 1 ) {
 		return this._settings[ name ]; // TODO: we should consider returning a deep copy if settings are allowed to be objects, not just primitives, in order to avoid unintentional mutation
 	}
 	value = arguments[ 1 ];
 	f = SETTINGS_VALIDATORS[ SETTINGS[ name ].type ];