dgadd add
Add Diffgazer registry items to your project.
Usage
Before publication: Diffgazer packages are not yet published to npm, so there is no dgadd bin until you install one. Follow the canonical Copy-first mode procedure to build and pack @diffgazer/add, then install that packed tarball in the target app. The target-app install is what puts dgadd on pnpm exec.
Items are namespaced as <namespace>/<item>. Bare names are rejected so install paths stay explicit:
Options
--all selects only items marked public. Hidden dependencies required by those items are still installed as transitive items, while standalone hidden add-ons are not selected by --all.
Keyboard integration
copy mode installs bundled hook source into your app.
keys mode rewrites local hook imports to @diffgazer/keys and installs the package dependency. Use it when the target app can resolve @diffgazer/keys.
Standalone hooks can be installed directly. They are copied as source files and have no runtime dependency on @diffgazer/keys:
Provider-backed hooks (useKey, useScope, useScopedNavigation, useActionRowNavigation, useFocusZone) are package-only because they depend on KeyboardProvider runtime context.
Notes
dgaddcopies source files into your project; you own the installed code.- UI dependencies and internal component dependencies are resolved automatically.
- Package-mode keys integration is separate from the
diffgazerproduct CLI.