Stop throwing in frontend code

[dshaw]

Throwing in Javascript and not handling the exception stops the execution engine, which means that the app will become unresponsive to users and it will be difficult to gracefully recover.

Proposed strategy:

• Create a new Plausible event for “throw” since this will provide insight into how often the app is stopping due to existing code
  • This can be done before rearchitecting the thrown code’s user experience flows that follow
• Assess if the existing throws actually need to stop the user experience
• If the throw does not need to stop the user experience, implement a try/catch to handle the throw and implement a recovery strategy.
• If the throw represents a point in the application state in which the app experience cannot recover:
  • coredump
  • Present the user with the error screen and the ability to refresh their application
• Additionally, @jessfraz proposes implementing a linting rule to prevent throwing in React (components).

Known Instances:

• /src/hooks/useBackdropHighlight.ts [Removed in Remove useBackdropHighlight #2323]
• /src/clientSideScene/sceneEntities.ts 2X
• /src/components/ActionButton.tsx
• /src/editor/plugins/lsp/server-capability-registration.ts
• /src/editor/plugins/lsp/codec/demuxer.ts
• /src/editor/plugins/lsp/kcl/semantic_tokens.ts
• /src/hooks/useRefreshSettings.ts
• /src/lang/modifyAst.ts 2X
• /src/lang/queryAst.ts
• /src/lang/wasm.ts 7X
• /src/lang/std/engineConnection.ts 6X
• /src/lang/std/fileSystemManager.ts - Tauri related. May not apply.
• /src/lang/std/sketch.ts 17X
• /src/lang/std/sketchcombos.ts 2X
• /src/lang/std/sketchConstraints.ts
• /src/lib/coredump.ts 8X
• /src/lib/createMachineCommand.ts
• /src/lib/exampleKcl.ts
• /src/lib/screenshot.ts 2X
• /src/lib/testHelpers.ts 3X - probably not important since test related
• /src/machines/authMachine.ts

• NOTE: Throwing in tests is fine.

Additional context about throwing in React/Javascript:

• How to handle errors in React