Collider: A package and dependency manager for Meson (wrap-based)

Name: Collider: A package and dependency manager for Meson (wrap-based)
Availability: InStock
Author: mog_dev

by mog_dev·Mar 9, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●SolidNiche GemSolve My Problem

Meson dependency manager with lockfiles and version constraints, but niche audience limits reach.

Strengths

•Closes a real gap in Meson's wrap ecosystem: lockfiles and version constraints were missing, enabling reproducible builds and CI clarity.
•Transitive dependency resolution via meson.build scanning is clever; WrapDB-compatible so zero migration friction for existing projects.
•Self-hosted repository support with built-in HTTP server and offline caching reduces infrastructure complexity.

Weaknesses

•Extremely narrow niche: only useful to Meson users publishing packages; mainstream C++ tooling (CMake, Conan, vcpkg) already solve this.
•Early maturity: v1.0.1 with minimal GitHub presence; no evidence of adoption beyond author's robotics projects.

Post Description

I built Collider because I needed a way to use and push my own artifacts in Meson projects. WrapDB is fine for upstream deps, but I wanted to publish my packages and depend on them with proper versioning and a lockfile, without hand-editing wrap files.

Collider builds on Meson’s wrap system: you declare deps in collider.json, run collider lock for reproducible installs, and push your projects as wraps to a local or HTTP repo. It’s compatible with WrapDB, so existing workflows still work: you just get a clear way to use and push your own stuff. Apache-2.0.