This roadmap outlines the planned features, improvements, and milestones for the development of PackageNinja. It will be updated regularly to reflect progress and new priorities.
- Basic CLI functionality
-
init
command for setting up.pkgninja
file -
sync
command for syncingpackage.json
and.pkgninja
files -
check
command for detecting outdated dependencies -
lock
andunlock
commands for dependency management -
update
command for upgrading packages that are unlocked
-
- Dependency categorization (upToDate, canUpdate, outdated)
- VSCode extension for workspace integration
- Dependencies versions history
- Reports formatted in :
- JSON
- HTML
- XML
- Enhanced CLI output with better color coding and formatting
- Improved error handling and messages
- Interactive prompts for user inputs
- Support for additional package managers (e.g., Yarn, pnpm)
- Auto-fix command for automatically updating dependencies
- Customizable config options for
.pkgninja
file
- Performance improvements for large projects
- Caching mechanism to reduce network requests
- Parallel processing for faster dependency checks
- Implement automatic updates for PackageNinja CLI
- Notification system for available updates
- Changelog generation for each new version
- Update documentation to reflect new features and changes
- Integration with popular CI/CD tools
- Web-based dashboard for visualizing project dependencies
- Community plugin system for extending PackageNinja functionality
- Detailed analytics and reports on dependency usage
We welcome contributions from the community! If you are interested in contributing, please check out our contributing guidelines for more information.
Your feedback is important to us. If you have any suggestions or find any issues, please open an issue on GitHub.
PackageNinja is licensed under the MIT License. See the LICENSE file for more details.
- D-C-MATE (owner of TechFever)
Special thanks to the open-source community for their invaluable resources and support.