feat(view): add browse-registry section to /wheels/packages (#2271 partial)#2277
Merged
Conversation
Proposes the approach for #2271: wheels.dev/packages listing+detail pages plus a "Browse registry" section on the in-app /wheels/packages view. Two separate fetchers (wheels.dev RegistryClient; in-app reuses the CLI's Registry.cfc directly) against the same GitHub registry, 24h cache, CLI-only install path.
Revises the Phase 4 spec after discovering wheels.dev is now four Astro static sites under web/sites/, not a CFML app. The in-app browse-registry section ships first; the wheels.dev Astro work needs its own brainstorm against the new architecture (build-time fetch + repository_dispatch). Adds the implementation plan for the in-app half.
This was referenced Apr 24, 2026
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
1 participant
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
/wheels/packageslisting packages available from wheels-dev/wheels-packagesRegistrycomponent — same data source aswheels packages list, 24h app-scope cachePublic.cfc's$blockInProduction()gate plus a view-level env check keep this off production serverswheels packages install <name>snippet✓ Installedbadge instead of the snippetwheels new-generated user apps where the CLI isn't on the classpath — installed-packages table still renders normallyScope
This is the in-app half of #2271. The
wheels.dev/packagesstatic-site work is deferred — original design assumed a live CFML app, butwheels.devwas migrated to four Astro static sites underweb/sites/with Cloudflare Pages deploys. That piece needs its own brainstorm against the new architecture (build-time fetch,repository_dispatchtrigger from the registry repo, etc.). See the "Revision" note indocs/superpowers/specs/2026-04-23-wheels-packages-phase4-ui-design.md. #2271 stays open.Changes
Three logical layers:
CLI —
cli/lucli/services/packages/Registry.cfc: newlistAll()returning[{name, description, tags, latestVersion, homepage}, ...]. Skips malformed manifests; propagates unavailability. Covered by newRegistryListAllSpec.cfc(3itblocks).Framework helper —
vendor/wheels/Public.cfc: new$loadRegistryPackages()returning{packages, error}. Production short-circuit, memoized Registry onapplication.wheels.$packageRegistry, typed-only catches (Wheels.Packages.*) so real bugs bubble up, classpath-availability guard for user apps. Covered by newLoadRegistryPackagesSpec.cfc(4itblocks) withFakeRegistry.cfc+PublicWithoutRegistry.cfcfixtures.View —
vendor/wheels/public/views/packagelist.cfm: new cfscript block + new section. 3-way conditional (error / empty / table).HTMLEditFormaton all DOM interpolations;JSStringFormatin the onclick; homepage links gated to^https?://;aria-labelon the Copy button.Test plan
bash tools/test-local.sh— 3324 pass, 0 fail, 0 error (Lucee 7 + SQLite)/wheels/packageson a local LuCLI server renders 200 with all 4 live registry packages and 4 install snippets✓ Installedbadge on that row (not rerun this session — covered by the UI logic path in specs)Spec & plan
docs/superpowers/specs/2026-04-23-wheels-packages-phase4-ui-design.mddocs/superpowers/plans/2026-04-23-wheels-packages-phase4-inapp.mdRefs #2271, #2243, #2233