Home
Home copied to clipboard
Project Glimpse: Node Edition - Spend less time debugging and more time developing.
**Repro Steps:** 1. Open up [this URL](stickerapp.azurewebsites.net/create) 2. Launch the Glimpse client 3. Select the request which corresponds to the `/create` route 4. Click the expand/collapse icon for the first...
**Repro Steps:** 1. Navigate to [this URL](http://stickerapp.azurewebsites.net/create) 2. Launch the corresponding Glimpse client 3. Select the request which corresponds to the `/create` route 4. Hover your mouse over the "heading"...
The Filter section currently shows up in the Data tab even though there is no content. Please hide the Filter bar when there is no known operation across all requests....
In order to spot potential performance optimizations, it would be pretty awesome to see whether a database call was using an efficient index or not, based on seeing the difference...
**Repro steps:** 1. Add a MongoDB call to an app's route (I'm using Mongoose, but it shouldn't matter) 2. Run the app to exercise that call 3. Open up the...
I'm sure this is already planned for accessibility/etc., but as a "keyboard-preferred" user, I just wanted to log the request to be able to fully navigate the UI via the...
I'm not even sure whether what Glimpse already shows for Mongo operations isn't sufficient, but I couldn't help but wonder whether the difference between Mongoose code and the underlying MongoDB...
Glimpse did a really great job capturing logs messages, however, I was left wondering of what to do next with that information ... It would be **super helpful** if we...
After installing the latest Mongoose, as well as Glimpse Node package, the following two logs show up in nearly all of my requests:  Neither of these are actionable for...
**Update (4:01 PM 9/19/2016)** - This same issue impacts the `res.links` method as well, and has the same odd display as the `res.cookie` method. --- **Repro steps:** 1. Write a...