fix(cli): add 'droid' to valid AI types#192
Open
tonymfer wants to merge 1 commit intonextlevelbuilder:mainfrom
Open
fix(cli): add 'droid' to valid AI types#192tonymfer wants to merge 1 commit intonextlevelbuilder:mainfrom
tonymfer wants to merge 1 commit intonextlevelbuilder:mainfrom
Conversation
The source code already includes 'droid' in AI_TYPES, AI_FOLDERS, detect.ts, template.ts, and the droid.json platform config. However, npm package v2.2.3 was published before these additions, so `uipro init --ai droid` fails with "Invalid AI type: droid". Bumping version to 2.2.4 ensures the next publish includes droid support. Also adds 'droid' to package.json keywords. Closes nextlevelbuilder#172 Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
accesspath27-lgtm
approved these changes
Mar 20, 2026
accesspath27-lgtm
left a comment
accesspath27-lgtm
left a comment
There was a problem hiding this comment.
Review: fix(cli): add 'droid' to valid AI types
APPROVE — Minimal, well-documented fix.
- Clean version bump (2.2.3 → 2.2.4) +
droidkeyword addition incli/package.json - No source code changes — just ensures the next publish includes already-written
droidsupport - Follows semver patch conventions, closes #172
- Essentially zero risk
One note: confirm the publish workflow rebuilds dist/ from current source (not cached) when publishing 2.2.4.
Contributor
|
@claude review |
|
Claude Code is working… I'll analyze this and get back to you. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
droidAI type support in the published npm packagedroidto package.json keywordsWhy
The README documents
uipro init --ai droidas a supported command, but the published npm package (v2.2.3) rejects it with "Invalid AI type: droid".Root cause: The source code already has full
droidsupport (type definition,AI_TYPESarray,AI_FOLDERSmapping, detection logic, platform template, and config). However, the npm package v2.2.3 was published before these additions were made — the compileddist/index.jsin the published tarball hasAI_TYPESwithoutdroid.The fix is a version bump to 2.2.4 so that the next
npm publishrebuildsdist/from the current source and includesdroid.Closes #172
Test plan
droidis inAI_TYPESarray (cli/src/types/index.ts)droidis inAI_FOLDERSmapping (cli/src/types/index.ts)droiddetection incli/src/utils/detect.tsdroiddescription ingetAITypeDescription(cli/src/utils/detect.ts)droidinAI_TO_PLATFORMmapping (cli/src/utils/template.ts)cli/assets/templates/platforms/droid.jsonexistsdroidfrom compiledAI_TYPESuipro init --ai droidwill no longer return an error🤖 Generated with Claude Code