Showing posts from August, 2016

How I Learned To Stop Worrying and Love Vim Plugins

I switched to Vim 6 years ago because I wanted to keep my dev setup as lean as possible. I was tired of working in heavy IDEs and wanted a light and fast environment without all the bells and whistles.

Originally, I avoided any plugins that fundamentally changed the editor. If it wasn’t a < ~5 line function I could code myself or crib from Vim’s help command, it wasn’t going in my vimrc.

Here are some minor improvements that helped me early on: Jumping to the beginning and end of function blocks when writing Perl and JavaScriptAutocomplete via tab via vim help’s CleverTab function Reformat & syntax check my code with Vim’s equalprgcoupled with Perl::Tidyand JS-Beautify.
The Problem:

As the codebase I was working on at the time grew, I started feeling the limitations of my self-imposed rules. Finding related files when editing the rapidly growing codebase was becoming a chore.
Hmm.. Was that function in /API/Controllers/ /API/Validation/ /Web/Controller/API/…


With the new release of the BugReplay extension, we’ve added one of the most requested features/bug fixes, built in source map support for console logs.

If you are using React or otherwise minifying your javascript you may have noticed your stack traces look different in Chrome (or another browser that supports source maps) than in the detail pane of a console log entry in BugReplay.

This is because Chrome natively parses source maps (, which is an index which a parser can use to look up the original file, line and column that a line in a minified file came from.

Recordings made with the new extension - which Chrome will download and install automatically - will upload relevant sourcemaps, and the detail pane for a javascript log entry will display the stack trace through the source map.