Implement automatic rebuild and browser reload during development:
- File watcher monitors .go files for changes with configurable extensions
- Builder compiles Go source to WASM on file changes
- LiveReload WebSocket server notifies connected browsers to reload
- DevServer combines all components for easy development setup
- HTML injection adds reload script automatically
Usage:
dev := host.NewDevServer("public", "index.html", ".", "public/app.wasm")
dev.ListenAndServe(":8080")
Closes#9
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Replace direct internal/element usage with public ui package
components to ensure examples only use the public API:
- Add ui.RawCheckbox for plain checkbox without label wrapper
- Add ui.Span for span elements with text content
- Add View.TextDecoration modifier for strikethrough styling
- Update todo example to use these public components
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This example demonstrates Iris reactive patterns:
- Signal holding a slice/list of todos
- Adding and removing items dynamically
- Component composition (inputRow, todoList, todoItem)
- Input handling with TextInput and Enter key support
- Conditional rendering (empty state, strikethrough for completed)
Closes#5
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Address review feedback to include a decrement button that
demonstrates reactive updates in both directions.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Basic example showing:
- Creating a signal with NewSignal
- Reading value with Get()
- Writing value with Set()
- Button click handler
- Reactive text that updates when signal changes
Closes#4
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This example demonstrates all key Iris features for internal tool teams:
- Multiple pages with client-side routing
- Auth-protected sections with route guards
- Reactive data display with signals
- Form inputs (text, checkbox, slider, select)
- Component composition with reusable layouts
Test credentials: admin/admin (full access) or user/user (limited access)
Closes#8
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add a comprehensive example showing client-side routing:
- Router setup with multiple routes (/, /about, /users, /admin)
- Route parameters (/users/:id) with the NumericIdGuard
- Navigation using Link component and programmatic Navigate/Back
- Route guards with AuthGuard for protected admin page
- Browser history integration with back/forward support
Closes#6
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Documents the host package covering:
- Basic server setup with code example
- Directory structure for WASM apps
- Static file serving and SPA fallback
- WASM MIME type configuration
- Automatic gzip compression
- Development vs production considerations
Closes#3
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Minimal Iris application demonstrating:
- Signal creation with NewSignal
- Reactive text rendering with TextFromFunction
- Auto-incrementing counter to show reactivity
Closes#2
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Add explicit mkdir -p public before wasm_exec.js copy
- Specify to save app code as main.go
- Specify to save server code as server.go
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Provides a complete getting-started guide covering prerequisites,
app creation, HTML host setup, build commands, and running the app.
Closes#1
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Remove test step from CI (WASM-only code can't run native tests)
- Update manifesto links to use absolute Gitea URLs
Co-Authored-By: Claude <noreply@anthropic.com>
