This content originally appeared on DEV Community and was authored by Tajudeen Abdulgafar
Following my previous blogs, I released version 0.0.1 of the Repository Context Packager.
What’s New
Core Features
- Full and summary output modes (summary is 85% smaller)
- Token estimation for LLM context management
- Smart file filtering (excludes node_modules, lock files)
- Multi-language support
Community Contributions
David Humphrey fixed the installation instructions in the README. Simple but important – documentation matters.
David Rivera added the recent file filter feature. Now you can use --recent [days] to only include files modified within a specified timeframe. Defaults to 7 days if no number provided. This is useful when you want to focus on recent changes rather than the entire codebase.
npm start . --recent 3 # Files from last 3 days
npm start . --recent # Files from last 7 days (default)
Technical Implementation
The recent filter works by checking file modification times against a cutoff date. It filters files during the collection phase, so it’s efficient even on large repositories.
Added proper error handling for the recent flag – validates that the input is a positive number and provides clear error messages.
Installation
git clone https://github.com/abdulgafar4/repo-context-packager.git
cd repo-context-packager
npm install
npm run build
Usage
npm start . # Package current directory
npm start . --summary # Summary mode
npm start . --recent 5 # Recent files only
npm start . --tokens --max-tokens 50000 # With token limits
This release establishes a solid foundation for the tool with useful community-driven features.
Give It a Shot
As always, the tool is open source, so grab it and see if it’s useful. Add issues, solve issues, and add features. And if you build something cool to scratch your own itch, let me know – I’m always curious what problems other developers are solving.
GitHub: Repo-Context-Packager.
This content originally appeared on DEV Community and was authored by Tajudeen Abdulgafar