Description
The terminal sometimes hangs during WebContainer initialization or when running Clarinet commands (especially npm run test, npm i, or long compilations).
Current Behavior
- Terminal becomes unresponsive or shows loading spinner indefinitely
- WebContainer occasionally fails to load on first attempt
- No clear error message or retry mechanism when it fails
Expected Behavior
- Terminal should reliably initialize within 3–5 seconds
- Clear loading states and error messages should be shown
- Users should have a "Retry" button when initialization fails
- Better handling of long-running Clarinet commands with progress indicators
Why This Matters
A reliable terminal is critical for developer experience. Many new users abandon tools when the terminal fails on first use. This directly impacts adoption of LabSTX as a browser-based Clarity IDE.
Acceptance Criteria
- Terminal initializes successfully on 95%+ of page loads
- Clear error states and retry functionality implemented
- Progress indication for long Clarinet operations
- No indefinite hanging states
Description
The terminal sometimes hangs during WebContainer initialization or when running Clarinet commands (especially
npm run test,npm i, or long compilations).Current Behavior
Expected Behavior
Why This Matters
A reliable terminal is critical for developer experience. Many new users abandon tools when the terminal fails on first use. This directly impacts adoption of LabSTX as a browser-based Clarity IDE.
Acceptance Criteria