Alternatives
Products that do what LogRadar does
Stop Shipping Debug Code to Production
- 1AW
Hey HN, I wanted to show you a product a small team and I have been working on for 4 years. https://jam.dev It’s called Jam and it prevents product managers (like I used to be) from being able to create vague and un-reproducible bug tickets (like I used to create). It’s actually really hard as a non-engineer to file useful bug tickets for engineers. Like, sometimes I thought I included a screenshot, but the important information the engineer needed was what was actually right outside the boundary of the screenshot I took. Or I'd write that something "didn't work" but the engineer…
2024
- 2VD
2020 · github.com
- 3LL
Hey HN, I just built an experimental VSCode extension called LLM Debugger. It’s a proof-of-concept that lets a large language model take charge of debugging. Instead of only looking at the static code, the LLM also gets to see the live runtime state—actual variable values, function calls, branch decisions, and more. The idea is to give it enough context to help diagnose issues faster and even generate synthetic data from running programs. Here’s what it does: * Active Debugging: It integrates with Node.js debug sessions to gather runtime info (like variable states and stack traces). *…
2025 · github.com
- 4

- 5

- 6AV
2024 · github.com
- 7

- 8

A VS Code extension to track your 100 Days of Code progress.
2020
- 9

- 10AV
We made a VS Code extension [1] that lets you visualise logs and traces in the context of your code. It basically lets you recreate a debugger-like experience (with a call stack) from logs alone. This saves you from browsing logs and trying to make sense of them outside the context of your code base. We got this idea from endlessly browsing traces emitted by the tracing crate [3] in the Google Cloud Logging UI. We really wanted to see the logs in the context of the code that emitted them, rather than switching back-and-forth between logs and source code to make sense of what happened. It's a…
2025 · github.com
- 11

- 12VC
2020 · github.com
- 13

- 14VC
This is a spiritual adaptation of oil.nvim for vscode. The main idea is you edit the filesystem by editing the current directory listing's text buffer. For example, if I want to rename a file, I just rename it in the listing file. This is extremely powerful because it translates all of your text-editing skills immediately into file editing capabilities. Some features: * Create/rename/move/delete files by editing the current directory listing's textbuffer * Filter using glob pattern * Trash and undo support * Works even in remote-ssh workspaces * Works across multiple vscode…
2025 · github.com
- 15

- 16

- 17

- 18

- 19

- 20WM
2025 · omlet.dev
- 21

- 22VC
Instantly share code snippets from VS Code with shortcut. Supports all programming languages. No sign-up, no hassle. Perfect for quick code reviews, debugging, or showing off your work.
2025 · snippetshare.dev
- 23AV
I use print() a lot to debug small codebases. Log-booster VS Code extension allows you to insert/comment/uncomment/delete print statements within a Python file. If you happen to use it and like/dislike it, I would love to know. Inspiration: I discovered Turbo Console Log extension (https://github.com/Chakroun-Anas/turbo-console-log) and loved it. I noticed that it doesn't work for Python files. So I tried building one :)
2022 · github.com
- 24VT
Hi All, this is Shardul here - I am the co-founder of Videobug. https://bug.video We are super excited to share Videobug with you. Videobug records run time code execution so that developers can watch it line by line as frequently as they want, right in their IDE. It takes away the pain of recreating exact conditions that led to a bug and saves developer time in every bug squash. Parth (my co-founder) and I have worked on multiple production grade applications in startups and enterprises. We used Logrocket, Sentry, and Datadog for logging and found ourselves adding more logs after…
2022
Ranked by how close each launch is in meaning, then by votes. Refine with a description →