Summary
The install/usage path for non-Node repos is not obvious enough when teams only want Charter as local governance tooling.
What We Hit
In a C++ repo, we needed to determine:
- npm package name:
@stackbilt/cli
- binary names:
charter / stackbilt
- a robust local invocation pattern that does not depend on global install
Requested Improvement
Please add a concise "non-Node repo" quickstart section to README/docs, for example:
npm install --save-dev @stackbilt/cli@<version>
npx --no-install @stackbilt/cli doctor --adf-only
And optionally include a fallback note for WSL DrvFs (--no-bin-links) linked from this quickstart.
Why this helps
This reduces onboarding ambiguity for repos where Node is not the primary build system but Charter is required for governance.
Summary
The install/usage path for non-Node repos is not obvious enough when teams only want Charter as local governance tooling.
What We Hit
In a C++ repo, we needed to determine:
@stackbilt/clicharter/stackbiltRequested Improvement
Please add a concise "non-Node repo" quickstart section to README/docs, for example:
And optionally include a fallback note for WSL DrvFs (
--no-bin-links) linked from this quickstart.Why this helps
This reduces onboarding ambiguity for repos where Node is not the primary build system but Charter is required for governance.