update parser to handle variadic input

Author: steveswork

debug.js

@@ -1,2 +1,2 @@
 require = require( 'esm' )( module );
-require( './src/cli' ).runCli( `${ process.cwd() }/test/stub-modules/index.js` );
+require( './src/cli' ).runCli([ `${ process.cwd() }/test/stub-modules/index.js` ]);

package-lock.json

@@ -10,7 +10,8 @@
     "chalk": "^4.1.0",
     "esm": "^3.2.25",
     "lodash.get": "^4.4.2",
-    "lodash.isempty": "^4.4.0"
+    "lodash.isempty": "^4.4.0",
+    "strip-comments": "^2.0.1"
   },
   "devDependencies": {
     "@babel/core": "^7.12.10",

package.json

@@ -4,22 +4,25 @@
 
 **Install:** npm i -D @webkrafters/ordercss
 
-**Usage:**  `ordercss <main entry module path>`
+**Usage:**  `ordercss <...main entry module path>`
 
 # Intro
 
 This is a cli tool created to alleviate the CSS extraction conflict order issues encountered in next.js applications. It is intended to be run BEFORE the build process of next.js or similarly situated applications where the aforementioned CSS order conflict error is a concern.
 
 # Mechanics
 
-OrderCSS is designed to pull and organize in hierarchy all non-referenced CSS module imports from script files of .js, .jsx, .ts and .tsx modules found in the dependency graph of a main entry script module. The resultant organised CSS paths are listed in the terminal.
+OrderCSS is designed to pull and organize in hierarchy all non-referenced CSS module imports from script files of .js, .jsx, .ts and .tsx modules found in the dependency graph of a main entry script module. The resultant organised CSS paths are firstly listed in the terminal.
 
  - The usage of the term "non-referenced" refers to imports and requires statements and expressions made for their side effects as defined in the [MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Statements/import#Import_a_module_for_its_side_effects_only) 
 
-Additionally, a newly generated module is also installed within the same directory as the main entry script module to serve as a CSS manifest listing all non-referenced CSS module imports in the order of priority. All of the curated CSS paths are imported into the manifest module relative to the entry script module. The installed module is named in the following format:
+
+Additionally, a newly generated module is also installed within the same directory as the main entry script module to serve as a CSS manifest listing all non-referenced CSS module imports in the order of priority. All of the curated CSS paths are imported into the manifest module relative to the entry script module. **Where multiple path arguments are supplied, the CSS manifest module is created at the last argument directory** The installed module is named in the following format:
 
     <main entry script module filename>_css_manifest.<js or ts accoring to main entry script module extension>
 
+Please be sure to see the [Usage Steps](#usage-steps) section below for very crucial details.
+
 ## Special cases
 
 Any module import/require expression with path argument ***(better known as module name)*** without extension information is assumed to be either a direct script import with any of the following extensions **.js .jsx .ts .tsx** or a directory containing an index file with one of the four aforementioned extensions.
@@ -56,12 +59,17 @@ open the command line terminal
 
 cd into the project root or any other preferred location within the project.
 
-run `ordercss <main entry module path>`
+run `ordercss <...main entry module path>`
+
+#### The mainEntryModulePath Arguments
+
+The ordercss cli is variadic. The lone ***mainEntryModulePath*** is a required argument set bearing the file location(s) of one or many module(s) whose dependency graph(s) would be inspected for non-referenced css module imports and curated. The expected parameter value for each argument item is the absolute path to the entry module file or the entry module file path relative to the current working directory.
 
-#### The mainEntryModulePath Argument
+Note: the motivation behind the support for the variadic functionality is the accommodation for breaks in the in the import/require sequence. One good example of this is the disconnect between the next.js pages/_app.js and page/<specific_page>.js. For such a scenario, the following cli command is applicable:
 
-The lone ***mainEntryModulePath*** is a required argument bearing the file location of a module whose dependency graph would be inspected for non-referenced css module imports and curated. The expected parameter value is either the absolute path to the entry module file or the entry module file path relative to the current working directory.
+`ordercss <pages dirname>/pages/_app.js <pages dirname>/pages/<specific page>.js`
 
+The resolution of the arguments into a single heirarchized CSS import list is carried out in a LIFO manner. The resulting css manifest module is created for the module residing in and stored in the parent directory of the last path argument. 
 
 # Prologue
 

readme.md

@@ -6,9 +6,15 @@ import isEmpty from 'lodash.isempty';
 
 import { generateOutputModule, getCssImportOrder } from '.';
 
-export const runCli = entryModulePath => {
-	const realEntryPath = resolve( process.cwd(), entryModulePath );
-	const orderedCssPaths = getCssImportOrder( realEntryPath );
+const getAbsolutePath = (() => {
+	const cwd = process.cwd();
+	return path => resolve( cwd, path );
+})();
+
+/** @param {FilePath[]} entryModulePaths */
+export const runCli = entryModulePaths => {
+	const realEntryPaths = entryModulePaths.map( getAbsolutePath );
+	const orderedCssPaths = getCssImportOrder( realEntryPaths );
 	if( isEmpty( orderedCssPaths ) ) {
 		console.warn( chalk.yellow.bold(
 			'No compliantly commented CSS imports detected in the generated dependency graph.'
@@ -19,7 +25,7 @@ export const runCli = entryModulePath => {
 	console.log( orderedCssPaths.join( '\n' ) );
 	console.info( chalk.blue.bold( 'Listing completed.' ) );
 	try {
-		generateOutputModule( orderedCssPaths, realEntryPath );
+		generateOutputModule( orderedCssPaths, realEntryPaths.slice( -1 ).pop() );
 		console.log( chalk.green.bold( 'Module update completed.' ) );
 	} catch ( e ) {
 		console.log( '\n\n%s', chalk.yellow.bold( 'Unsuccessful module update attempt.' ) );
@@ -30,7 +36,7 @@ export const runCli = entryModulePath => {
 };
 
 const cli = () => {
-	const entryModulePath = process.argv[ 2 ];
+	const entryModulePath = process.argv.slice( 2 );
 	try {
 		if( isEmpty( entryModulePath ) ) {
 			throw new TypeError( 'No entry module path supplied.' );
@@ -45,3 +51,5 @@ const cli = () => {
 };
 
 export default cli;
+
+/** @typedef {import("./order-imports/index").FilePath} FilePath */

src/cli.js

@@ -27,8 +27,9 @@ const getCssModuleCalc = outputFilePath => {
 };
 
 /**
- * @param {FilePath} entryModulePath root module absolute path (in a next.js application: could refer to the current page module)
+ * @param {FilePath|FilePaths[]} entryModulePath root module absolute path(s) (in a next.js application: could refer to the current page module; perhaps preceded by the _app.js file path.)
  * @returns {FilePath[]} aggregated queue containing absolute paths to css import hierarchy from the leaf to the entry module.
+ * @see readme.md for further details on the entryModulePath argument
  */
 export const getCssImportOrder = entryModulePath => ( new Order( entryModulePath ) ).calculate();