monolithic repository manager
Well croc goes away from npm standard approach having packages in separated repositories. Instead all related packages can live in one repo so we can avoid endless cascading of commit, push, publish that usually happens if we need change package deep in our dependency tree.
Usage:
croc [options] ls [<package>...]
croc [options] deps [<package>...]
croc [options] exec CMD [<package>...]
croc [options] pexec CMD [<package>...]
croc [options] link
croc [options] (install | test | publish) [<package> ..]
Options:
-h, --help Show this screen.
-v, --version Show version.
--json Show information in JSON format.
-p, --predecessors Include projects depending on the packages.
-x, --strict Dependencies must statisfy version (semver)
-c, --changed Show only projects that is changed.
-s, --since=SHA Commit to diff against [default: master]
FAQs
monolithic repository manager
We found that croc demonstrated a not healthy version release cadence and project activity because the last version was released a year ago. It has 2 open source maintainers collaborating on the project.
Did you know?
Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.
Security News
Critics call the Node.js EOL CVE a misuse of the system, sparking debate over CVE standards and the growing noise in vulnerability databases.
Security News
cURL and Go security teams are publicly rejecting CVSS as flawed for assessing vulnerabilities and are calling for more accurate, context-aware approaches.
Security News
Bun 1.2 enhances its JavaScript runtime with 90% Node.js compatibility, built-in S3 and Postgres support, HTML Imports, and faster, cloud-first performance.