Merge pull request #221 from code-collabo/cleanup

Cleanup PR

Author: Ifycode

dev/cleanup.js

@@ -0,0 +1,56 @@
+import { readdirSync, rmdirSync } from 'fs';
+import { repo } from './developer';
+const { cwd, chdir } = process;
+
+// -------------------------------------------------------------------------------------------------
+// TODO 1 (after CLI upgrade): Configure cleanup to run using node-mongo command i.e. "node-mongo cleanup" not "npm run cleanup"
+// TODO 2 (if possible): (I don't think you will need this TODO when this is done using the "node-mongo cleanup" command - or it might need slight modification)
+            // update package.json cleanup script dynamically with the cleanup file path.
+            // This means you will have to get the cleanup file name/path dynamically too...
+// Or... (instead) should cleanup script be handled a pre-commit hook or pre-push hook or something? - We'll see...
+// -------------------------------------------------------------------------------------------------
+
+// cd into repo root
+chdir('../');
+
+// use repo root
+const rootDir = cwd();
+
+// return all files and folders in repo root i.e. original + node-mongo generated
+ const repoContent = readdirSync(rootDir, (err, filesAndFolders) => {
+    if (err) {
+      throw err;
+    }
+
+    return filesAndFolders;
+});
+
+console.log(repoContent);
+
+const filterContentToGetTheOnesGeneratedByCLI = repoContent.reduce((acc, curr) => {
+  if (!repo.originalContentList.includes(curr)) {
+    acc.push(curr);
+  }
+  return acc;
+}, []);
+
+console.log(filterContentToGetTheOnesGeneratedByCLI);
+
+// delete folders generated by CLI
+try {
+  filterContentToGetTheOnesGeneratedByCLI.map(folder => {
+    console.log(`${folder} folder deleted successfully`);
+    return rmdirSync(folder, { recursive: true, force: true });
+  });
+} catch (err) {
+  console.log(err);
+}
+
+console.log(repoContent);
+
+// ------------------------------------
+// TODO: Write another script at the end of this file
+// that updates this repoContent list back when done.
+// Is this TODO even needed? - We'll see. For now the
+// solution ending here works fine.
+// ------------------------------------

dev/developer.js

@@ -0,0 +1,41 @@
+import { basename, resolve, dirname } from 'path';
+// file to get and save if user still has the
+// Initial settings...
+
+const { chdir } = process;
+
+// Dynamically get current the name of this file you are in, and its parent folder
+const developerJsFileName = basename(__filename/*, extname(__filename)*/);
+const cleanupFolderPath = dirname(new URL(import.meta.url).pathname);
+
+// Change directory into the dynamically gotten parent folder, then extract folder name from path
+chdir(cleanupFolderPath);
+const cleanupFolderName = basename(resolve());
+
+// CLI repo's original content config object
+export const repo = {
+  hasOriginalContentOnly: true,
+  originalContentList: [
+    cleanupFolderName,
+    '.all-contributorsrc',
+    '.babelrc',
+    '.editorconfig',
+    '.eslintrc.json',
+    '.git',
+    '.github',
+    '.gitignore',
+    '.npmrc',
+    'LICENSE',
+    'README.md',
+    'bin',
+    'cleanup.js',
+    'node_modules',
+    'package-lock.json',
+    'package.json',
+    'spec',
+    'src',
+    'templates'
+  ],
+  developerJsFileName,
+  cleanupFolderName,
+}

package.json

@@ -16,7 +16,8 @@
     "test": "npm-run-all --parallel test-message dev-test",
     "dev-test": "nodemon --exec babel-node spec/run.js",
     "CI-test": "babel-node spec/run.js",
-    "test-message": "node -r esm src/customize/testMessage"
+    "test-message": "node -r esm src/customize/testMessage",
+    "cleanup": "node -r esm dev/cleanup.js"
   },
   "repository": {
     "type": "git",