Skip to content

wheels packages install <name> is a silent no-op — canonical install command in docs doesn't actually install #2706

@bpamiri

Description

@bpamiri

Severity: high — anyone following the canonical install instructions silently fails. Bad first impression for the entire 4.0 package system.

Surfaced by: titan Phase 2.1 (Wheels 4.0 upgrade), 2026-05-15.

Repro

$ wheels packages install wheels-sentry
Reading lucee.json...
Resolving dependencies...
ℹ️  No git or extension dependencies to install
$ echo $?
0

Exits 0. Reports success. Nothing was installed. vendor/wheels-sentry/ does not exist after the call.

The actual working command is wheels packages add wheels-sentry.

Two bugs in one

  1. install is a no-op pointing at the lucee.json dep-resolver instead of the registry installer. wheels packages install <name> is what every doc surface tells users to run:

    • wheels packages --help shows install <name> [--force]
    • PLAN.md-style upgrade guides
    • User muscle memory from npm/pip/etc.

    But the implementation routes install to the lucee.json resolver, which finds no git/extension deps to install, and exits cleanly.

  2. add works but isn't documented in wheels packages --help.

Suggested fix

One of:

  • Alias install to add (preferred — least breakage, matches docs).
  • Make install <name> fail loudly with an error pointing at add <name>.
  • Update --help to remove install and document add instead.

File: cli/lucli/Module.cfc (or wherever Module.packages action dispatch lives).

cc @bpamiri

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions