Help: FAQ
Use this FAQ workflow to resolve common Diwa setup and behavior questions quickly before opening a new issue.
Prerequisites
- - Know which section your issue belongs to (styles, components, or developing).
- - Reproduce the issue on current package versions.
- - Capture any console errors or failing test output.
Step 1: Check the matching docs section first
Most setup questions are covered in Getting Started, Developing, or Partials pages.
Start here:
- /
- /developing
- /partials
- /must-knowStep 2: Verify common setup pitfalls
Many issues come from missing styles, missing loader registration, or premature test assertions.
Quick checks:
- Token stylesheet loaded once
- Loader bootstrap runs once
- Tests wait for component readinessStep 3: Escalate with focused context
If unresolved, open support with concise diagnostics and links to checked docs pages.
Open support:
https://github.com/jortega0033/diwa-components/issues/newCommon Questions
- - Q: Why do components render but not behave? A: Loader registration likely did not run on the client.
- - Q: Why is styling inconsistent? A: Ensure global token stylesheet is loaded before interactive render.
- - Q: Why are tests flaky? A: Wait for custom-element definition and componentOnReady where needed.
- - Q: Where do breaking changes appear? A: Use News > Changelog and Migration Guide.
Troubleshooting
- - If FAQ items repeat in support, convert them into clearer docs snippets.
- - If setup differs by framework, compare with the specific Developing page.
- - If issue appears after upgrade, inspect changelog and migration guidance first.