Posts Tagged: npm

Make Git Bash Awesome Again

Add some spice to git bash to help battle the cubicle blues.

Add some sweet ascii art

Edit your ~/.bashrc file and add the following

cat << EOF

<insert ascii art here>


Spice up the prompt

This one is a little more tricky, but start by editing the C:\Program Files\Git\etc\profile.d\

You will see a line that starts


Edit this line to make whatever your heart desires. Here is a fun one that creates the shrug emoji.

PS1='\[\033]0;$TITLEPREFIX:${PWD//[^[:ascii:]]/?}\007\]' # set window title
PS1="$PS1"'\n'                 # new line
PS1="$PS1"'\[\033[32m\]'       # change to green
PS1="$PS1"'\u@\h '             # user@host<space>
PS1="$PS1"'\[\033[35m\]'       # change to purple
PS1="$PS1"'¯\(°_o)/¯ '         # shrug
PS1="$PS1"'\[\033[33m\]'       # change to brownish yellow
PS1="$PS1"'\w'                 # current working directory

Working with Themes in Hapi.js

npm version

This plugin will add a view handler to Hapi.js routes to serve themeable content. This allows you serve different stylesheets by theme name, serve different layout files, or whatever you need.

Content can be themed by url (default), http header, or a custom function.


By default, the handler will read the “theme” key from the url by taking the first url segment after the domain. For example, if your app has the following url:

The theme key would be batman and the theme file that will be loaded is batman.json.

NOTE: The theme key will be stripped out of the url when it is passed to the Hapi.js router. This allows for flexibility when creating routes, since you will not have to account for the theme name in your url matching.

Example Theme File

Theme files can contain any information you want, but must at least maintain key and isDefault properties.

    "key": "batman",
    "isDefault": true,
    "brandName": "Batman Crimefighting",
    "logo": "logo-batman-134x23.png",
    "logoAltText": "Batman (TM)"

When loaded by the theme key, this theme file is injected as a js object into the view and can be used by the templating engine.

<link rel="icon" type="image/png" href="images/{{theme.favicon}}" />
<link rel="stylesheet" type="text/css" href="css/themes/{{theme.key}}/styles.css" />


Each theme is stored in a theme file, loaded with glob pathing, and configured like any other plugin.

var themes = {
    register: require('hapi-themes'),
    options: {
        configFilePath: '**/*.theme.json'

server.register([themes], function(err){
    // ...
        // ...    

Specify the view handler for a route.

    method: 'GET',
    path: '/',
    handler: {
        theme: {
            template: 'index',
            layout: 'default',
            relativeTo: Path.join(__dirname, 'server/views')

Using an http header as the theme key

If you want to use an http header as the theme key, you can set the following options.

var themes = {
    register: require('hapi-themes'),
    options: {
        configFilePath: '**/*.theme.json',
        defaultThemeKey: 'HEADER_THEME_KEY',
        keyStrategy: 'header'

Using a custom function for theme resolution

You can also specify a custom function that should return a string equivalent to the name of the theme file to load. The keyStrategy takes the Hapi.js request object as its parameter and must return a string.

var themes = {
    register: require('hapi-themes'),
    options: {
        configFilePath: '**/*.theme.json',
        keyStrategy: function(request){
            return 'batman';