Lux Package Manager

[keithharvey]

Include the Lux package manager so that we can manage packages. Updates the README and adds core testing dependencies. Lux seems like it is set to become the de facto package manager for lua and it is also not luarocks.

Lux Docs

You can run lux update then immediately run busted, which whines there's no specs folder

See downstream Unit Testing PR, which should be merged at the same time as this.

[WatchTheFort]

Still need to look at the readme changes later

[NortySpock]

Looks like the actual CLI command is lx , so it would be lx update , not lux update

lx update
⠁ 📥 Downloading rockspec for busted==5ed85d0e016a5eb5eca097aa52905eedf1b180f1

But otherwise this does do what you mentioned -- it downloads the busted library without complaining.

[keithharvey]

Looks like the actual CLI command is lx , so it would be lx update , not lux update

Good call, fixed this in the readme, I had it aliased

[github-actions]

Test Results

16 tests  ±0   7 ✅ ±0   3s ⏱️ ±0s
 1 suites ±0   9 💤 ±0 
 1 files   ±0   0 ❌ ±0 

Results for commit a2ede82. ± Comparison against base commit cf64f44.

♻️ This comment has been updated with latest results.

[keithharvey]

Both this and Unit Test Bootstrapping are ready to go as far as I know. I updated the README with max-jobs beta from my travails in WSL trying to get lux update not to deadlock. But I think we're good to go here and I can help support this if anyone has any problems.

[keithharvey]

I’d suggest planning the full Lux transition in two phases for smoother adoption:

Phase 1 (this PR):

• Introduce the Busted testing framework
• Keep Lux optional and test it with a small group of devs to gauge friction
• Limit usage to “extras” such as unit tests and code formatting tools

Phase 1.5 (i18n prep):

• Add a dependency for kikito/i18n
• Trace current i18n usage and document any behavior that relied on our fork (API, interpolation, pluralization, defaults, fallbacks)
• Decide: short-lived compatibility shim vs. direct fixes in callers (record the choice and scope)
• Add CI guardrails: fail on missing keys/unsafe interpolation; add a short migration checklist for contributors

Phase 2 (future work / includes recoil changes):

• Update Recoil CI to publish recoil-lua-library as a Lux package, and ensure the code generation produces a canonical Lua rock/package directory structure.
• Add a dependency so that BAR consumes that published package, and remove the recoil-lua-library submodule.
• Announce that Lux is now a required part of the toolchain (Discord, announcements, monthly meetings, etc.)
• (Recommended) fix all lx check errors and warnings, then enforce lx check && lx fmt succeeding in the CI and popularize commit hooks
• (Recommended) Align BAR’s directory layout with the canonical Lua rock/package directory structure.
  We could support a transition period where Recoil loads both src/luarules and luarules, then — with the next engine version — finalize with a git mv into src/ in BAR. Rebases and merges should track across the move cleanly.

[NortySpock]

LGTM