Skip to main content

Using Sublime Text 2 Build Systems, NodeJS and Mocha

Recently, I've been switching between TextMate and Sublime Text 2. The latest feature I've been using quite a bit on NodeJS projects is the Sublime Text 2 Build Systems. Although I don't specifically use the "NodeJS Build System", I do use the Make version with a minor edit to how it pipes its commands through shell instead of its own sandboxed way of doing things. This enables the build system to leverage your current bash settings.

Below is a screenshot of my Sublime Text set to Make build system:


Below is a screen shot of what was changed (~/Library/Application Support/Sublime Text 2/Packages):


A Sublime Text 2 build system is a preconfigured plugin for Sublime Text with associated keybinds to make running tests, compiling the project, and deploying your application easier. It's a productivity monster. People who come from the Visual Studio or Eclipse (Java) world will love it as running your GNU make build system can be as easy as +B (if you're on OS X).

This is the result:


Hope that helps!

If you're wondering what my Makefile has, it's a simple one that invokes Mocha and points to the tests directory, as well as, changes the reporter to be less chatty.

Post a Comment

Popular posts from this blog

TextMate Tutorial: How to add a Strikethrough keybind to your Markdown bundle

Markdown is awesome for quickly generating Readme's on Github. After looking at other projects using the strike tag, I've decided to create a custom keybind for it in my TextMate Markdown bundle. Here's how:

1) Click the + sign on the bottom left and click New Command.
2) Paste this into the editbox and make sure you name your command "Strikethrough".

For the input field, select WORD in the drop down.
For the output field, select "insert as snippet".
As for the keybind, you can totally map it to whatever you're comfortable with but I chose Command-D as it is the same thing in Microsoft Word.

Cheers,
Jaime

World of Warcraft Ninjalist addon: version 0.1 coming along quite nicely

After toying around with more GUI related issues in World of Warcraft's API, I've decided to take a totally different direction. Originally when I architected this addon, I knew in my mind it would be a super simple Console application that a user could easily paste in a name and add it to the database; however, why stop there?

After discovering AceGUI, I can easily start developing UI components in no time! As of right now, I've got it saving data in between game sessions--the interesting part will come when I'll have to develop the web service that will parse the SavedVariable.lua, eliminate duplicate entries, as well as, do a huge merge between their copy and whats on the server's (per realm basis of course).

Here's a screen shot of the responses when adding new Ninjas to your list:
When a user clicks add after entering a name in the textbox, it'll go ahead and add that person to the ninjalist tagging the user's realm and current date/time. Someday, I…

Using Git Hooks: Prepare Commit Message to automatically prepend branch names on commit messages

When you're practicing branch by feature with distributed version control, typically you'll get assigned a ticket or issue and that ends up being your feature branch. Instead of always typing in the branch name in every commit, you can edit your Git hooks (specifically prepare-commit-msg).

Assuming that this is a brand new git repository:

mv .git/hooks/prepare-commit-msg.sample .git/hooks/prepare-commit-msg
vi .git/hooks/prepare-commit-msg

Edit the file by commenting out what was originally in the file and then add this:



Now, whenever you make a commit, it should show up like this in the log:



Since GitHub and Bitbucket both support Emojis inside commit messages, you can do something cute like this



Want more emojis? check out the Emoji Mardown Cheatsheet!