Skip to content

chore(deps): update frontend npm dependencies #463

chore(deps): update frontend npm dependencies

chore(deps): update frontend npm dependencies #463

Triggered via pull request September 7, 2026 17:01
Status Success
Total duration 3m 28s
Artifacts –

ci-ui.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
react(set-state-in-effect): src/components/waveform/RegionEditor.tsx#L39
src/components/waveform/RegionEditor.tsx:39:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/pages/VoiceLibraryPage.tsx#L143
src/pages/VoiceLibraryPage.tsx:143:24: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/components/audio/AudioDeck.tsx#L104
src/components/audio/AudioDeck.tsx:104:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/components/OmniVoice/ClipPlayer.tsx#L30
src/components/OmniVoice/ClipPlayer.tsx:30:7: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/components/StitchTimeline.tsx#L1463
src/components/StitchTimeline.tsx:1463:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/components/StitchTimeline.tsx#L26
src/components/StitchTimeline.tsx:26:24: Calling setState synchronously within an effect can trigger cascading renders
react(immutability): src/components/StitchTimeline.tsx#L403
src/components/StitchTimeline.tsx:403:43: Cannot access variable while it is being initialized
react(immutability): src/components/StitchTimeline.tsx#L383
src/components/StitchTimeline.tsx:383:43: Cannot access variable while it is being initialized
react(set-state-in-effect): src/hooks/use-mobile.ts#L14
src/hooks/use-mobile.ts:14:5: Calling setState synchronously within an effect can trigger cascading renders
react(set-state-in-effect): src/pages/SpeakPage.tsx#L47
src/pages/SpeakPage.tsx:47:24: Calling setState synchronously within an effect can trigger cascading renders