CommandCodeAI / CommandCodeAI/command-code
Need to handle mods with code compilations errors on build and load
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
I built a mod, but while the cmd mods list showed it as available in the project, the command it had did not appear.
Turns out there was a compilation issue, but I had no way of knowing:
in the @.commandcode/mods/erd.ts there should be comands but i have reloaded but i dont see them available. but i see it is available cmd mods list
Built-in mods (4)
provider-anthropic · builtin
provider-copilot · builtin
provider-openai · builtin
update-notice · builtin
Mods (1)
erd · project
✻ Thought for 1 second [ctrl+o to expand]
⠶ Let me look at your mod file and check the Command Code mod docs to figure out why the commands aren't appearing.
READ [.commandcode/mods/erd.ts] 1011 lines
✻ Thought for 6 seconds [ctrl+o to expand]
⠶ Let me check if there's a TypeScript compilation issue or missing dependency.
SHELL [ls ~/projects/dthyresson/erd-mod/node_modules/@commandcode/harness 2>&1 | head -5]
│ ls: /Users/dthyresson/projects/dthyresson/erd-mod/node_modules/@commandcode/harness: No such file...
└ ... [ctrl+o to expand]
SHELL [ls ~/projects/dthyresson/erd-mod/schema/ 2>&1]
└ schema.sql
SHELL [node -e "try { require('~/projects/dthyresson/erd-mod/.commandcode/mods/erd.ts'); } catch(e) { co...]
│ Invalid regular expression: /^\s*\S+\s+([A-Za-z_]+(?:\s*\([^)]*(?:\([^)]*\)[^)]*)*\))?(?:\s|$)/i:...
└ ... [ctrl+o to expand]
✻ Thought for 29 seconds [ctrl+o to expand]
⠶ Found the issue. The regex on line 115 has an unmatched parenthesis — the capture group ( is never closed, making the regex invalid. This causes the mod to fail
to load entirely, which is why /cmd mods list shows it but none of its commands appear.
Expected Behavior
- the mod builder should run some type or compile checks
- on load of the mod, warn that a mod failed to load so can correct (or status of disable due to error)
- something to know while mod isn't working/available
Actual Behavior
- mod listed but commands it implements not present
Steps to reproduce the issue
- use mod builder but introduce some type or build compilation error in it
Command Code Version
1.5.0
Operating System
macOS
Terminal/IDE
ghostty
Shell
zsh
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure using the malformed regex reported at line 115 of .commandcode/mods/erd.ts, then trace how the mod builder and cmd mods list handle the failed load. Done means compilation or load errors are surfaced clearly and the mod's unavailable or disabled status is visible instead of listing it as usable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100