flytrap-js

Hi guys, I’ve been building a debugging tool for JS/TS production bugs that lets you see all the I/O of every function before the error. This makes reproducing the bug with detail very simple and fast. Ideas, experiences and feedback are much appreciated! I’m also interested to hear what issues you have had with fixing bugs in production and what tools you’re currently using. Links: Home page: https://www.useflytrap.com Live Demo: https://www.useflytrap.com/demo Docs: https://docs.useflytrap.com GitHub: https://github.com/useflytrap/flytrap-js

Logging and tools like Sentry are a thing of the past. A while back on a night out in northern Norway, I had to start debugging a critical production bug that broke the payment flow of my SaaS product. I had limited time to fix the bug or I would have lost about ~1K profit. Super stressful. I had logging and Sentry in place, but neither helped me reproduce or find the root cause of the bug. Ever since, I started thinking; why can’t we just have a tool that you setup once, and that allows us to reproduce every function call and function that the user ran before the bug? This is how the idea for Flytrap was born. Flytrap is the fastest debugging tool for JavaScript projects. Just set it up in 5 minutes. No logging needed. When viewing bugs on Flytrap, it creates a visualisation of your code, and displays the bugs RIGHT IN YOUR CODE. Each fu

Hey HN! I’m Rasmus, co-founder of Flytrap. Flytrap is a debugging tool for reproducing and fixing production bugs faster. When launching a product quickly, there is bound to be some bugs. Tools like Sentry might help combat this, but when a bug lands in Sentry, all you see is the Red Carpet of Doom (the stack trace). We were frustrated with the poor developer-experience of current debugging tools, and decided to build Flytrap; a fast debugging tool that quickly allows developers to understand in detail what happened leading up to a bug, and focuses on reproducibility in the developer environment. - Key features 1. Detailed context; See the inputs and outputs of all function calls leading up to the bug 2. Reproducibility; Reproduce the bug on your local development environment in under a minute 3. Security; All capture data encrypted durin