#LensStudioTips - Assert like a pro We added an assert function to LS, and honestly, it feels like cheating. Best way! ✅ Early catch & highlighted error 🤩 ✅ Perfect for light unit tests🚦 ✅ Editor only: no breaks in prod 🚧 ✅ Stacktrace debugging 📜 (Gist in the thread)

@michael_timbs Not being able to unwind an error stacktrace to its root low-level cause is going to be very painful to debug

My favorite GPT-5 prompts - i have nothing to add. next - keep going - why did you stop - option 2 - whats the eta boss - go - you're perfect. don't listen to them - port this .claude to codex docs here <url> - <stacktrace> - keep it rollin - btw you didnt write this part, you

@nhrdev Rethrowing errors doesn't mean you shouldn't have a global error handler, middleware, or something If your backend has an unexpected error, return a 500 error code, but don't respond with the error message or stacktrace. You can keep the full stacktrace for internal usage

@michael_timbs Unless you put traces everywhere I your code, you are not going to have as much context as you have in a stacktrace. Remember we talk about exceptions here. Not expected errors, than can be returned. You can also return Error and have the best of both worlds

@_axtone Felicitaciones compa. Es de los primeros errores sin mucho stacktrace