Skip to content

fix(cli): add 'droid' to valid AI types#192

Open
tonymfer wants to merge 1 commit into
nextlevelbuilder:mainfrom
tonymfer:fix/add-droid-ai-type
Open

fix(cli): add 'droid' to valid AI types#192
tonymfer wants to merge 1 commit into
nextlevelbuilder:mainfrom
tonymfer:fix/add-droid-ai-type

Conversation

@tonymfer

Copy link
Copy Markdown

Summary

  • Bump CLI version from 2.2.3 to 2.2.4 to include droid AI type support in the published npm package
  • Add droid to package.json keywords

Why

The README documents uipro init --ai droid as 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 droid support (type definition, AI_TYPES array, AI_FOLDERS mapping, detection logic, platform template, and config). However, the npm package v2.2.3 was published before these additions were made — the compiled dist/index.js in the published tarball has AI_TYPES without droid.

The fix is a version bump to 2.2.4 so that the next npm publish rebuilds dist/ from the current source and includes droid.

Closes #172

Test plan

  • Verified droid is in AI_TYPES array (cli/src/types/index.ts)
  • Verified droid is in AI_FOLDERS mapping (cli/src/types/index.ts)
  • Verified droid detection in cli/src/utils/detect.ts
  • Verified droid description in getAITypeDescription (cli/src/utils/detect.ts)
  • Verified droid in AI_TO_PLATFORM mapping (cli/src/utils/template.ts)
  • Verified cli/assets/templates/platforms/droid.json exists
  • Confirmed published npm tarball v2.2.3 is missing droid from compiled AI_TYPES
  • After version bump and rebuild, uipro init --ai droid will no longer return an error
  • Other AI types unaffected

🤖 Generated with Claude Code

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 accesspath27-lgtm left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Review: fix(cli): add 'droid' to valid AI types

APPROVE — Minimal, well-documented fix.

  • Clean version bump (2.2.3 → 2.2.4) + droid keyword addition in cli/package.json
  • No source code changes — just ensures the next publish includes already-written droid support
  • 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.

@mrgoonie

Copy link
Copy Markdown
Contributor

@claude review

@claude

claude Bot commented Mar 24, 2026

Copy link
Copy Markdown
Contributor

Claude Code is working…

I'll analyze this and get back to you.

View job run

@ia-abatista

Copy link
Copy Markdown
Contributor

Recommend closing, @mrgoonie. The droid AI type already works on main, and the version-bump mechanism is moot now that #375/#384 republish the package automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

uipro init --ai droid` returns "Invalid AI type: droid"

4 participants