binary-collections 2.0.9 → 2.0.11

package/readme.md

@@ -1,6 +1,5 @@
 # Binary Collections
-
-A comprehensive collection of Node.js CLI tools designed to streamline common development workflows. This toolkit provides utilities for git operations, dependency management, build processes, and various development automation tasks.
+A comprehensive toolkit of Node.js CLI utilities for streamlining development workflows. Includes tools for git operations, dependency management, build processes, automation, and more.
 
 ## Features
 
@@ -28,7 +27,17 @@ npm install binary-collections -g
 npm install binary-collections@https://github.com/dimaslanjaka/bin/raw/master/releases/bin.tgz
 ```
 
-## VS Code Setup
+### Direct run
+
+```bash
+# Yarn berry
+yarn dlx binary-collections@https://raw.githubusercontent.com/dimaslanjaka/bin/master/releases/bin.tgz <command-name>
+
+# NPX
+npx -y binary-collections@https://raw.githubusercontent.com/dimaslanjaka/bin/master/releases/bin.tgz <command-name>
+```
+
+## VSCode Setup
 
 Create `.vscode/settings.json` to add binary tools to your PATH:
 
@@ -72,8 +81,8 @@ Create `.vscode/settings.json` to add binary tools to your PATH:
 
 ### Quick Reference
 
-| Category | Tools | Description |
-|----------|-------|-------------|
+| Category | Commands | Description |
+|---|---|---|
 | **Git** | `git-purge`, `git-diff`, `git-fix`, `git-reduce-size` | Git repository management and optimization |
 | **Submodules** | `submodule`, `submodule-install`, `submodule-remove`, `submodule-token` | Git submodule operations |
 | **NPM Scripts** | `nrs`, `run-s`, `run-series`, `npm-run-series` | Run npm scripts in series with pattern matching |
@@ -82,51 +91,25 @@ Create `.vscode/settings.json` to add binary tools to your PATH:
 | **Process Mgmt** | `kill-process`, `nodekill`, `javakill`, `del-ps` | Process management and termination |
 | **File System** | `rmfind`, `rmpath`, `rmx`, `print-tree`, `dir-tree` | File system operations |
 | **Cleanup** | `del-nodemodules`, `del-yarncaches`, `del-gradle` | Cache and build directory cleanup |
-| **GitHub Actions** | `clean-github-actions-caches`, `clean-github-actions-cache`, `clear-github-actions-cache`, `clear-github-actions-caches`, `clear-gh-caches` | Remove old GitHub Actions caches, keep only the latest |
-
-
----
-#### Binary List Generation & Source Code
-
-The list of available binaries and utilities is automatically generated by the build script (`build.js`).
-All CLI tools and binaries are collected from the `bin/`, `lib/`, and other relevant folders. The build process updates the `bin` field in `package.json` to reflect all available executables.
-
-Source code for utilities is located in the [`src/`](./src/) folder. To update the binary list, run:
-
-```bash
-yarn run build
-# or
-node build.js
-```
-
-This will scan the project and update `package.json` with all available binaries. The list may change as files are added or removed from the project.
-
-For a complete list of available binaries and utilities, see:
-- [Binary executables](https://github.com/dimaslanjaka/bin/tree/master/bin)
-- [Library modules](https://github.com/dimaslanjaka/bin/tree/master/lib)
-- [Package configuration](https://github.com/dimaslanjaka/bin/blob/master/package.json)
+| **GitHub Actions** | `clean-github-actions-caches`, `clean-github-actions-cache`, `clear-github-actions-cache`, `clear-github-actions-caches`, `clear-gh-caches` | Remove old GitHub Actions caches, keep only latest |
 
 ### Git Tools
 
 #### Git Repository Purge
 Clean and optimize git repositories by pruning reflogs:
-
 ```bash
 git-purge
 ```
-
 ![Git purge screenshot](https://github.com/dimaslanjaka/bin/assets/12471057/2805c54e-28a7-491d-b381-de2593a854b3)
 
 #### Git Diff Utility
 Enhanced git diff functionality:
-
 ```bash
 git-diff
 ```
 
 #### Git Fix Utility
-Comprehensive Git configuration fixer for cross-platform development (replaces the old `git-fix-encoding`):
-
+Comprehensive Git configuration fixer for cross-platform development (replaces `git-fix-encoding`):
 ```bash
 git-fix                          # Apply all fixes
 git-fix --lf-only                # Force LF line endings only
@@ -137,7 +120,6 @@ git-fix --user NAME EMAIL        # Configure Git user with specific values
 git-fix --user --update-remote   # Also update remote URL to match user
 git-fix --user NAME EMAIL --update-remote  # Configure user and update remote URL
 ```
-
 Features:
 - Forces LF line endings (`core.autocrlf = false`)
 - Ignores file permission changes (`core.filemode = false`)
@@ -162,7 +144,6 @@ User Configuration:
 
 #### Git Repository Size Reducer
 Reduce git repository size by cleaning up history:
-
 ```bash
 git-reduce-size
 ```
@@ -183,16 +164,13 @@ git-reduce-size
 Run multiple npm scripts in series with pattern matching support.
 
 #### Options
-
-| Flag | Description |
-|------|-------------|
-| `--yarn` | Use `yarn run <script-name>` instead of npm |
-| `--verbose`, `-v` | Enable verbose output |
+| Flag                | Description                                 |
+|---------------------|---------------------------------------------|
+| `--yarn`            | Use `yarn run <script-name>` instead of npm |
+| `--verbose`, `-v`   | Enable verbose output                       |
 
 #### Example
-
 Execute all scripts matching the pattern `namescript:**`:
-
 ```json
 {
   "name": "package-name",
@@ -213,14 +191,12 @@ Execute all scripts matching the pattern `namescript:**`:
 
 #### Yarn Package Reinstaller
 Reinstall yarn packages with dependency type flags:
-
 ```bash
 yarn-reinstall <packageName> [--dev|-D|--peer|-P|--optional|-O]
 ```
 
 #### Package Resolutions Manager
 Manage package resolutions in package.json (aliases: `pkg-resolutions-updater`, `pkg-res-updater`):
-
 ```bash
 pkg-resolutions-updater
 pkg-res-updater
@@ -230,7 +206,6 @@ pkg-res-updater
 
 #### Node Modules Finder
 Find all node_modules directories in a project:
-
 ```bash
 find-node-modules      # Library function
 find-node-modules-cli  # CLI tool
@@ -246,7 +221,6 @@ find-nodemodules       # Alias
 
 #### Process Killers
 Kill processes by name or pattern:
-
 ```bash
 kill-process    # General process killer
 nodekill        # Kill Node.js processes
@@ -261,39 +235,21 @@ del-ps          # Kill processes by command name
 
 ### Cleanup Tools
 
-### GitHub Actions Cache Cleaner
-
-Remove old GitHub Actions caches, keeping only the most recent cache for each prefix:
-
-```bash
-clean-github-actions-caches
-```
-
-Features:
-- Authenticates using `ACCESS_TOKEN` or `GITHUB_TOKEN` from your `.env` file
-- Automatically groups and deletes caches by prefix, keeping only the latest
-- Works for the current repository (origin remote)
-
-Environment setup:
-- Ensure your `.env` file contains `ACCESS_TOKEN` or `GITHUB_TOKEN`
-
-Source: [`src/clean-github-actions-caches.cjs`](./src/clean-github-actions-caches.cjs)
+#### GitHub Actions Cache Cleaner
+[See full documentation](./docs-src/clean-github-actions-caches.md).
 
 #### Node Modules Cleaner
 Remove node_modules directories recursively:
-
 ```bash
 del-nodemodules        # Primary command
 del-node-modules       # Alternative
 clean-nodemodule       # Legacy
 clean-nodemodules      # Legacy
 ```
-
 ![Node modules cleaner screenshot](https://github.com/dimaslanjaka/bin/assets/12471057/f03e5b51-1808-4e82-a474-0dd3c7eab5fe)
 
 #### Yarn Cache Cleaner
 Clear yarn cache directories:
-
 ```bash
 del-yarncaches         # Primary command
 del-yarn-caches        # Alternative
@@ -301,26 +257,25 @@ del-yarn-caches        # Alternative
 
 #### Gradle Build Cleaner
 Delete gradle build folders:
-
 ```bash
 del-gradle
 ```
 
+#### Free ChatGPT automation tool
+
+[See full documentation](./docs-src/free-chatgpt.md)
+
 ## Troubleshooting
 
 ### Submodule Installation Issues
-
 If you encounter the following error:
-
 ```log
 fatal: 'origin/<branch>' is not a commit and a branch '<branch>' cannot be created from it
 fatal: unable to checkout submodule '<folder>/<submodule>'
 ```
-
 **Solution**: Delete `.git/modules` directory before running `submodule-install`.
 
 #### Complete Submodule Setup Example
-
 ```bash
 echo "Initializing submodules..."
 git submodule init
@@ -331,12 +286,30 @@ git submodule sync
 git submodule foreach "git submodule sync"
 
 echo "Updating submodules..."
-mkdir -p bin >/dev/null 2>&1
-curl -L https://github.com/dimaslanjaka/bin/raw/master/bin/submodule-install > bin/submodule-install
-rm -rf .git/modules
-bash ./bin/submodule-install
+npx --yes rimraf .git/modules
+npx --yes binary-collections@https://raw.githubusercontent.com/dimaslanjaka/bin/master/releases/bin.tgz submodule-install
 ```
 
+## Binary List Generation & Source Code (Development)
+
+The list of available binaries and utilities is auto-generated by the build script ([`build.mjs`](./build.mjs)).
+- All CLI tools and binaries are collected from the `bin/`, `lib/`, and other relevant folders.
+- The build process updates the `bin` field in `package.json` to reflect all available executables.
+- Source code for utilities is located in the `src/` folder.
+
+To update the binary list, run:
+```bash
+yarn run build
+# or
+node build.mjs
+```
+This scans the project and updates `package.json` with all available binaries. The list may change as files are added or removed.
+
+See also:
+- [Binary executables](https://github.com/dimaslanjaka/bin/tree/master/bin)
+- [Library modules](https://github.com/dimaslanjaka/bin/tree/master/lib)
+- [Package configuration](https://github.com/dimaslanjaka/bin/blob/master/package.json)
+
 ## Contributing
 
 Contributions are welcome! Please feel free to submit a Pull Request.

package/releases/readme.md

@@ -0,0 +1,36 @@
+# Release `binary-collections` tarball
+## Releases
+| version | tarball url |
+| :--- | :--- |
+| latest | https://github.com/dimaslanjaka/bin/raw/6b683c8/releases/bin.tgz |
+| latest | https://github.com/dimaslanjaka/bin/raw/master/releases/bin.tgz |
+
+use this tarball with `resolutions`:
+```json
+{
+  "resolutions": {
+    "binary-collections": "<url of tarball>"
+  }
+}
+```
+
+## Releases
+
+    ## Get URL of `binary-collections` Release Tarball
+- select tarball file
+![gambar](https://user-images.githubusercontent.com/12471057/203216375-8af4b5d9-00c2-40fb-8d3d-d220beaabd46.png)
+- copy raw url
+![gambar](https://user-images.githubusercontent.com/12471057/203216508-7590cbb9-a1ce-47d6-96ca-8d82149f0762.png)
+- or copy download url
+![gambar](https://user-images.githubusercontent.com/12471057/203216541-3807d2c3-5213-49f3-b93d-c626dbae3b2e.png)
+- then run installation from command line
+```bash
+npm i https://....url-tgz
+```
+for example
+```bash
+npm i https://github.com/dimaslanjaka/nodejs-package-types/raw/main/release/nodejs-package-types.tgz
+```
+
+## URL Parts Explanations
+> https://github.com/github-username/github-repo-name/raw/github-branch-name/path-to-file-with-extension

package/requirements.txt

@@ -0,0 +1 @@
+psutil

package/test/README.md

@@ -0,0 +1,101 @@
+# Git-Fix Test Suite
+
+This directory contains comprehensive tests for the `git-fix` utility and its related modules.
+
+## Environment Configuration
+
+The test suite properly reads the `.env` file from the project root to load environment variables:
+- `GITHUB_USER` - Used for git user.name configuration
+- `GITHUB_EMAIL` - Used for git user.email configuration
+
+This ensures tests run with the same environment as the actual application.
+
+## Test Files
+
+### 1. `git-fix.test.js`
+**Main unit tests for the git-fix CLI utility**
+- Tests command-line argument parsing (`--help`, `-h`, `--user`, etc.)
+- Tests option combinations (`--lf-only`, `--permissions`, `--normalize`)
+- Tests user configuration with CLI arguments and environment variables
+- Tests error handling for invalid arguments and non-git repositories
+- Tests summary message output
+- Uses extensive mocking to isolate the CLI logic
+
+### 2. `git-utils.test.js`
+**Unit tests for the git utility functions**
+- Tests `runGitCommand()` function with success/failure scenarios
+- Tests `isGitRepository()` function
+- Tests error handling and console output
+- Mocks `child_process` functions
+
+### 3. `git-user-config.test.js`
+**Unit tests for the git user configuration module**
+- Tests user configuration with CLI arguments vs environment variables
+- Tests precedence (CLI args override environment variables)
+- Tests partial configuration (username only, email only)
+- Tests whitespace handling and trimming
+- Tests error scenarios when git commands fail
+
+### 4. `git-fix-integration.test.js`
+**Integration tests using real git repositories**
+- Creates temporary git repositories for testing
+- Tests actual git configuration changes
+- Tests `.gitattributes` file creation and modification
+- Tests real git config values (`core.autocrlf`, `core.eol`, etc.)
+- Tests console output and error handling
+- More realistic testing but slower than unit tests
+
+### 5. `test-helpers.js`
+**Test utility functions**
+- `createTempGitRepo()` - Creates temporary git repositories for testing
+- `cleanupTempDir()` - Cleans up test directories
+- `getGitConfig()` - Reads actual git configuration values
+- `gitAttributesContains()` - Checks .gitattributes file content
+- Helper functions for mocking `process.argv`
+
+## Running Tests
+
+```bash
+# Run all git-related tests
+yarn test --testNamePattern="git"
+
+# Run specific test files
+yarn test git-fix.test.js
+yarn test git-utils.test.js
+yarn test git-user-config.test.js
+yarn test git-fix-integration.test.js
+
+# Run with coverage
+yarn test:coverage
+
+# Run in watch mode
+yarn test:watch
+```
+
+## Test Coverage
+
+The test suite covers:
+- ✅ Command-line argument parsing
+- ✅ Help system (`--help`, `-h`)
+- ✅ All CLI options and combinations
+- ✅ User configuration (CLI args + environment variables)
+- ✅ Git repository detection
+- ✅ Error handling and edge cases
+- ✅ Console output and logging
+- ✅ Real git configuration changes (integration tests)
+- ✅ File system operations (.gitattributes creation)
+
+## Test Structure
+
+- **Unit tests** use extensive mocking to test logic in isolation
+- **Integration tests** use real git repositories to test actual functionality
+- **Helper functions** provide reusable utilities for test setup and cleanup
+- All tests use Jest with proper setup/teardown for clean testing environment
+
+## Notes
+
+- Integration tests create temporary directories in the system temp folder
+- All tests clean up after themselves (no leftover files or directories)
+- Console output is mocked in tests to avoid cluttered test output
+- Environment variables are properly reset between tests
+- Tests work on both Windows and Unix-like systems

package/test/package.json

@@ -1,5 +1,6 @@
 {
-  "name": "test",
+  "name": "binary-collections-test",
+  "private": true,
   "version": "1.0.0",
   "description": "",
   "main": "index.js",

package/test-project/readme.md

@@ -0,0 +1,26 @@
+# Test Project
+
+This project is intended to be run separately from the parent project. To set up an isolated environment with Yarn, follow these steps:
+
+## Steps
+
+1. **Create an empty `yarn.lock` file:**
+
+  ```sh
+  cd /d:/Repositories/binary-collections/test-project
+  type nul > yarn.lock
+  ```
+
+2. **Initialize a new Yarn project:**
+
+  ```sh
+  yarn init -y
+  ```
+
+3. **Install dependencies as needed:**
+
+  ```sh
+  yarn add <package-name>
+  ```
+
+This ensures the `test-project` has its own dependency tree, separate from the parent project.

package/tmp/test-repo/README.md

@@ -0,0 +1,35 @@
+# A Git(Hub) Test Repository
+
+Hey! This is my personal Git(Hub) Test Repository where I experiment with Git and GitHub. 
+
+If you are new to Git and GitHub and found this repository through Google: feel free to clone the repository and experiment with it! You will not be able to push back to the repository, as it is *my* repository and I cannot let everybody push to it. The right way to do it on GitHub is: 
+
+1. fork the repository in your own account, 
+2. make changes and push them in a branch of your own fork, 
+3. create a Pull Request in my repository. 
+
+I will get notified, will review the changes that you propose, and eventually will either merge the changes, or reject them. This *may* take some time as I am not actively monitoring nor maintaining this repository, as you can guess, but I try to be helpful ;)
+
+> NOTE
+> If you want your PR to have a chance to get merged, please propose additions or changes to neutral files such as text files or small images. If you propose changes to the GitHub workflow files, to `.gitignore`, etc. they will quite probably be rejected.
+
+Don't expect to find anything meaningful nor useful in the repository. Also, I happen to force-push a reset of everything from time to time. This means that I reset all history, including changes that you may have submitted. In theory, noone ever does this to a repository. But hey, this is a *test* repository after all.
+
+The rest of this README file is mostly random stuff.
+
+Clone the repository with: `git clone https://github.com/zpqrtbnk/test-repo.git .`
+
+We have test GitHUb pages (from the `gh-pages` branch) at: http://zpqrtbnk.github.io/test-repo/ 
+
+We have an image in the README (markdown)
+![Image](https://raw.github.com/zpqrtbnk/test-repo/master/wtf.jpg)
+
+We have an image in the README (html)
+<img src="./wtf.jpg" />
+
+We have an image in the README (more html)
+<p align="center" style="background:#000;padding:5px;color:#fff;font-size:150%;margin-bottom:64px">
+    <img src="./wtf.jpg" />
+    <span style="margin-left:48px;">wubble</span>
+</p>
+

package/tmp/test-repo/package.json

@@ -2,6 +2,6 @@
   "name": "test-repo",
   "packageManager": "yarn@4.9.2",
   "dependencies": {
-    "binary-collections": "D:\\Repositories\\binary-collections\\releases\\bin.tgz"
+    "binary-collections": "D:/Repositories/binary-collections/releases/bin.tgz"
   }
 }