FS size checker

A lightweight CLI tool for analyzing file and directory sizes. Signals errors via standard exit codes when specified size limits are exceeded

---

Features

• [x] Check sizes of files and directories
• [x] Set size limits and get warnings when exceeded
• [x] Configurable via command-line arguments
• [x] Cross-platform path handling (works on Windows, macOS, and Linux)
• [x] Configurable via a configuration file
• [x] Use regex patterns to match specific files
• [x] Ignore specific files or directories from size calculations.
• [x] Colorized output for better readability
• [x] Support for multiple units of measurement (B, KB, MB, GB, TB)
• [x] Check sizes for multiple files or directories in a single run

Legend:

• [x] Implemented feature
• [ ] Planned feature

Installation

Use via npx (No Installation Required)

You can use fs-size-checker directly with npx without installing it globally:

npx fs-size-checker <path> <max_size> <unit> <ignore>

You can install fs-size-checker globally using npm:

npm install -g fs-size-checker

Or, if you prefer to use it as a development dependency in your project:

npm install --save-dev fs-size-checker

Usage

Basic Usage

Run fs-size-checker from the command line:

fs-size-checker <path> <max_size> <unit> <ignore>

Example:

fs-size-checker ./dist 50000 B

This command checks if the ./dist directory exceeds 50000 B.

As an npm Script

Add fs-size-checker to your package.json for automated checks:

{
  "scripts": {
    "check-size": "fs-size-checker ./dist 50000 B"
  }
}

Run it with:

npm run check-size

Examples:

1. Directory Size Check in Bytes:

     fs-size-checker --path ./dist --max-size 50000 --unit B
   

2. File Check:

     fs-size-checker --path ./dist/index.js --max-size 1000 --unit B
   

3. Checking by specific paterns with a size limit in bytes:

   1. Check all JavaScript files in the 'dist' directory:

     fs-size-checker --path "dist/*.js" --max-size 500 --unit B
   

   2. Check all TypeScript files in the 'dist' directory and its subdirectories:

     fs-size-checker --path "dist/**/*.ts" --max-size 500 --unit B
   

   3. Check all JPEG and PNG images in the 'dist' directory and its subdirectories:

     fs-size-checker --path "dist/**/*.(jpeg|png)" --max-size 500 --unit B
   

   4. Check all chunked JavaScript files in the 'dist' directory that follow the pattern chunk-*.js:

     fs-size-checker --path "dist/chunk-*.js" --max-size 200 --unit B
   

4. Using the ignore argument to exclude specific files or directories:

   1. Ignore a specific files (e.g., .DS_Store) while checking JavaScript files:

     fs-size-checker --path dist --max-size 1 --unit MB --ignore .DS_Store
   

   2. Ignore multiple specific files and directories:

     fs-size-checker --path dist --max-size 1 --unit MB --ignore .DS_Store --ignore node_modules
   

Options

• --path or -p: The path to check. Can include directory and file matching patterns. Can be specified multiple times for checking multiple paths.
• --max-size or -m: The maximum allowed size (a positive number). Can be specified multiple times, corresponding to each path.
• --unit or -u: The unit for the size ( B ). If not specified, defaults to B (bytes). Can be specified multiple times, corresponding to each path.
• --ignore, -i Ignore files/directories (can be used multiple times)
• -c, --config <path>: Path to a custom configuration file
• --help or -h: Display the help message.

Configuration File

By default, fs-size-checker looks for a fs-size-checker.json file in the current directory. You can specify a custom configuration file using the -c or --config flag.

Example fs-size-checker.json:

{
  "sizeCheckList": [
    {
      "path": "bundle.min.js",
      "maxSize": 30,
      "unit": "KB",
      "ignore": []
    },
    {
      "path": "dist",
      "maxSize": 1,
      "unit": "MB",
      "ignore": [".DS_Store"]
    }
  ]
}

Cross-Platform Path Support

fs-size-checker supports cross-platform paths, so you can use it on Windows, macOS, and Linux without worrying about path separators:

# On Windows
fs-size-checker --path C:\Users\YourName\Documents --max-size 10000 --unit B

# On macOS or Linux
fs-size-checker --path /home/yourname/documents --max-size 10000 --unit B

Both of these commands will work correctly on their respective platforms.

Key Characteristics

• Zero Dependencies: This project is built without any external runtime dependencies, ensuring a lightweight and secure installation.
• Object-Oriented Programming (OOP) Approach: Utilizes OOP principles for better code organization, maintainability, and extensibility.
• TypeScript: Written in TypeScript for enhanced type safety and better developer experience.
• SOLID Principles: Adheres to SOLID principles of object-oriented design, promoting clean and maintainable code.
• Extensible Architecture: Designed with extensibility in mind, making it easy to add new features or modify existing ones.
• Cross-platform Compatibility: Works on Windows, macOS, and Linux operating systems.
• Comprehensive Test Suite: Includes a robust set of unit and integration tests to ensure reliability.
• Well-documented: Provides clear and comprehensive documentation for easy understanding and usage.

Security

• No execution of external code or scripts
• Strict input validation to prevent potential vulnerabilities
• Read-only operations ensure no modifications to your file system

Exit Codes and Error Handling

fs-size-checker uses exit codes to communicate the result of the size check:

• Exit code 0: All checked paths are within their specified size limits.
• Exit code 1: One or more checked paths exceed their specified size limits, or an error occurred during execution.

When a size limit is exceeded, fs-size-checker will:

1. Print a warning message to the console for each path that exceeds its limit.
2. Continue checking all specified paths.
3. Exit with code 1 after all checks are complete, if any limits were exceeded.

This approach ensures that:

• All specified paths are checked, even if earlier ones exceed their limits.
• The tool provides immediate feedback for each exceeded limit.
• Scripts or CI/CD pipelines can easily detect when any limit has been exceeded.

Development

To set up the project for development:

1. Clone the repository
2. Install dependencies: npm install
3. Build the project: npm run build
4. Run tests: npm test

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

---

⭐ Support This Project

If you find this project useful, please consider giving it a star on GitHub! 🌟

Your support helps others discover this project and keeps me motivated to improve it further. Thank you! 😊

License

This project is licensed under the MIT License. See the LICENSE file in the project root for the full license text.

The MIT License is a permissive license that allows for reuse with few restrictions. It permits use, modification, distribution, sublicense, and private use, provided that the license and copyright notice are included in all copies or substantial portions of the software.