Complete source on github.
I’m a big fan of not using the latest and greatest right out of the gate. I prefer to let other people work through the initial bugs and get a few examples documented before I jump in. It’s worked quite well for me thus far.
That said, I recently came across the need to set up a new angular project (client need). And I do like to explore new frameworks/methodologies/techniques/etc. once they’ve had some time to mature. Having not yet used browserify, this seemed like a good enough reason as any to give it a go. I have previously used requireJs in my angular projects, so I thought this would be a good opportunity for comparison.
After looking around for examples I quickly realized that, as to be expected, there are quite a few different ways to make this work… And, I didn’t really like any of them. I had some concerns that browserify would abstract the angular code too much. I wanted things to stay as traditionally angularish as possible. The eventual handoff will be to angular developers who may or may not have experience with browserify – so I want to keep things as simple as possible. Since none of the examples I found fit the bill, here’s what I came up with.
Gulp vs. package.json
While considering whether or not to migrate my build-steps into package.json exclusively, I thought about the pros/cons around using a task-runner like gulp as opposed to managing everything through package.json and npm scripts.
Ultimately, the big selling points for me about using gulp is its configurability and its cross-platform support. I develop on a mac, yet a majority of our clients use windows machines. There are some issues with some of the npm scripts on windows. Additionally, when you only install gulp locally, you have complete control over which version is installed – which can be very important when delivering your code to clients.
One of the issues I’ve found with gulp is the necessity of globally installing another package. It adds another hurdle to setting up the dev environment, which while small, adds up. That said, I’ve recently come across a method for running gulp without having to install it globally.
Check it out!
I’ve written and shared my git workflow a couple times, but only privately. I’ve been meaning to write more about it and share it publicly for some time now. This workflow has worked very well for me for the past year or so, but I am by no means a git expert. Take a look and let me know what you think. I’m always open to hearing about other peoples’ workflows and suggestions. So much to learn – I’ve only scratched the surface.
"Efficiency is the path to godliness"
I have fallen in love with Sublime Text 3. I use it every day. I wish I could calculate the number of keystrokes I have saved by using it. It would surely be an enormous number at this point! I’d like to share some of my favorite tips and tricks. I hope you find some of these useful.
This first posting will focus on establishing an efficient workflow within Sublime Text itself. This includes built-in functionality and a few plugins(packages) that really impact efficiency with getting around the editor.
I keep thinking up ideas for things to write about. I keep saying to myself “that will make an excellent blog post”. And yet, I have had no outlet for such things. It is long-since-past time to start a legit blog. I’m keeping this short and sweet. Much more to come…