Support, Changelog & Reporting
Collect useful diagnostics, understand releases, and report product issues without exposing sensitive data.
On this page 5
What you will learn
- Prepare a reproducible issue report.
- Identify the installed version.
- Protect secrets in diagnostics.
Before requesting support
Confirm the issue on a clean branch when possible and run the standard diagnostics.
bash
node --version
pnpm --version
pnpm checkUseful issue report
A reproducible report reduces resolution time.
- Nexus version
- Node and pnpm versions
- Affected public route
- Expected result
- Actual result
- Minimal reproduction steps
- Relevant console or build error
- Desktop/mobile and theme state
Protect sensitive information
Remove tokens, cookies, customer records, internal hostnames, private repository links, environment values, and credentials before sharing logs or screenshots.
Read the changelog
CHANGELOG.md describes notable changes by version. Review it before applying an update, especially when shared CSS, routing, configuration, dependencies, or release tooling changed.