Update namespace

This commit reverts making the plot "namespace" something of a
hybrid, where it is both non-conventional (i.e., a function, not
an object) and conventional (i.e., has sub-namespace members).
This led to confusion when generating a tree bundle where we need
a more strict delineation to determine how to interpret. As it
was, when generating a tree bundle, the hybrid nature of the
namespace led to attempting to overwrite a read-only property,
thus causing the bundle to error and, effectively, be unusable.

Author: kgryte

lib/node_modules/@stdlib/plot/lib/index.js

@@ -34,33 +34,9 @@
 
 // MODULES //
 
-var setReadOnly = require( '@stdlib/utils/define-read-only-property' );
 var plot = require( '@stdlib/plot/ctor' );
 
 
-// MAIN //
-
-/*
-* When adding modules to the namespace, ensure that they are added in alphabetical order according to module name.
-*/
-
-/**
-* Top-level namespace.
-*
-* @namespace ns
-*/
-var ns = plot;
-
-/**
-* @name sparklines
-* @memberof ns
-* @readonly
-* @type {Namespace}
-* @see {@link module:@stdlib/plot/sparklines}
-*/
-setReadOnly( ns, 'sparklines', require( '@stdlib/plot/sparklines' ) );
-
-
 // EXPORTS //
 
 module.exports = plot;

lib/node_modules/@stdlib/plot/test/test.js

@@ -21,7 +21,6 @@
 // MODULES //
 
 var tape = require( 'tape' );
-var hasOwnProp = require( '@stdlib/assert/has-own-property' );
 var Plot = require( '@stdlib/plot/ctor' );
 var plot = require( './../lib' );
 
@@ -38,8 +37,3 @@ tape( 'the main export is a plot constructor', function test( t ) {
 	t.strictEqual( plot, Plot, 'is alias' );
 	t.end();
 });
-
-tape( 'attached to the main export is a namespace containing sparkline functionality', function test( t ) {
-	t.strictEqual( hasOwnProp( plot, 'sparklines' ), true, 'has property' );
-	t.end();
-});