build: ensure correct operator precedence when using a dynamic require expression

lib/node_modules/@stdlib/_tools/repl-txt/rules/doctest/lib/main.js

@@ -70,7 +70,7 @@
 		var b;
 		var i;
 
 		// FIXME: clean-up this logic
 
 		if ( context.meta.filepath ) {
 			expected = [];
@@ -83,7 +83,7 @@
 			};
 			pkgName = pkg2alias( pkg ) || 'ALIAS';
 
 			// TODO: use @stdlib/utils/deep-set once refactored!
 			pkgName = pkgName.split( '.' );
 			N = pkgName.length;
 			o = scope;
@@ -98,7 +98,7 @@
 					o[ key ] = require( pkg ); // eslint-disable-line stdlib/no-dynamic-require
 				}
 			}
 			// TODO: process external aliases *BEFORE* creating the context (and also, what is going on here, given that the return value is ignored?)
 			vm.createContext( scope );
 
 			examples = section.examples;
@@ -165,12 +165,12 @@
 					return format( 'require(\'%s\')', pkg );
 				}
 				// If an alias does not exist in the global namespace, dynamically `require` a package so that the desired expression can be executed:
-				return format( 'require(\'%s\')', pkg );
+				return format( '(require(\'%s\'))', pkg );
 			}
 			alias = alias.split( '.' );
 			len = alias.length;
 
 			// TODO: use @stdlib/utils/deep-set once refactored!
 			o = scope;
 			for ( i = 0; i < len; i++ ) {
 				key = alias[ i ];

lib/node_modules/@stdlib/repl/help/scripts/build.js

@@ -90,7 +90,7 @@
 *
 * @private
 */
 function main() {
 	var related;
 	var fpath;
 	var alias;
@@ -180,11 +180,11 @@
 					// If an error was returned, we were unable to import the package...
 					if ( err instanceof Error ) {
 						debug( 'Unable to resolve package: %s.', p );
 						console.warn( 'WARNING: unable to resolve package `%s` for `%s`.', p, alias );
 						continue;
 					}
 					// If an alias does not exist in the global namespace, dynamically `require` a package so that the desired expression can be executed in example code:
-					file = replace( file, tmp[ j ], format( 'require(\'%s\')', p ) ); // WARNING: this assumes that `{{alias:}}` placeholders are in examples. If unresolved package identifiers are used in descriptions, this substitution is NOT appropriate. The use of such placeholders in description prose is uncommon, but not unheard of. However, given its relatively rare occurrence, we can likely be confident that this substitution is okay. Ideally, identifiers would be added to the database, so that this workaround is not necessary.
+					file = replace( file, tmp[ j ], format( '(require(\'%s\'))', p ) ); // WARNING: this assumes that `{{alias:}}` placeholders are in examples. If unresolved package identifiers are used in descriptions, this substitution is NOT appropriate. The use of such placeholders in description prose is uncommon, but not unheard of. However, given its relatively rare occurrence, we can likely be confident that this substitution is okay. Ideally, identifiers would be added to the database, so that this workaround is not necessary.
 					debug( 'Inserted a `require` expression for `%s`.', p );
 				} else {
 					file = replace( file, tmp[ j ], a );
@@ -236,7 +236,7 @@
 				continue;
 			}
 			if ( hasOwnProp( json, tmp ) ) {
 				// Concatenate associated signatures (e.g., same API, but multiple parameterizations based on argument types, etc):
 				json[ tmp ] += ast[ j ].raw;
 			} else {
 				json[ tmp ] = '\n' + ast[ j ].raw;