node package manager


Chrome/Javascript utilities


Author: Robert Ginda

There's not much in libdot that already exists. Not enough to justify an external dependency, at least. Here's the rundown...

lib.js (150 lines)                    - "var lib = {}" is the important part, followed by lib.registerInit() and lib.init().  The rtdep method is useful but hterm would still function if it were a no - op.
lib_colors.js (1k lines)              - The bulk of this file is color palettes.  The rest is a few simple utility functions
lib_f.js (280 lines)                  - Mostly trivial utility functions, plus a few that I've been carrying around for a decade or more.
lib_fs.js (280 lines)                 - HTML5 filesystem wrapper.  I don't think we'll find many implementations of this, since Chrome is the only browser that implements this API so far.
lib_message_manager.js (200 lines)    - Fairly trivial i18n message management that happens to work with Chrome's oddball message blobs.
lib_preference_manager.js (700 lines) - A preference manager pattern I've been using for the last decade, upgraded to work with localStorage and Chrome's sync storage APIs.
lib_storage_chrome.js                 - Storage adaptor for lib_storage.js.
lib_storage_local.js                  - Storage adaptor for lib_storage.js.
lib_storage_memory.js                 - Storage adaptor for lib_storage.js.
lib_test_manager.js (1k lines)        - A basic test manager that supports async tests and can be driven from the js console.
lib_utf8.js (155 lines)               - Simple utf8 encoder/decoder.

I don't see much in that list that I can take off the shelf. I'd need to see a patch showing some real advantages before considering a third party dependency.

(Also, fwiw, there's a few more libdot files in the pipeline, mostly of the "I've been using a library like this for a very long time and like it" variety.)

As far as making it more general and reusable, well, that's the idea. That's why I split these hterm specific files out into a common directory. I do intend to reuse libdot in my own Chrome apps projects, and would encourage a few others to try the same. If it starts running under its own power at some point then great. If not, hterm will still work.

What you need to build libdot

In order to build libdot, you need to have Node.js/npm latest and git 1.7 or later. (Earlier versions might work OK, but are not tested.)

Windows users have two options:

  1. Install msysgit (Full installer for official Git) and a binary version of Node.js. Make sure all two packages are installed to the same location (by default, this is C:\Program Files\Git).
  2. Install Cygwin (make sure you install the git and which packages), and a binary version of Node.js.

Mac OS users should install Xcode (comes on your Mac OS install DVD, or downloadable from Apple's Xcode site) and Homebrew. Once Homebrew is installed, run brew install git to install git, and brew install node to install Node.js.

Linux/BSD users should use their appropriate package managers to install git and Node.js, or build from source if you swing that way. Easy-peasy.

Install the grunt-cli package so that you will have the correct version of grunt available from any project that needs it. This should be done as a global install:

npm install -g grunt-cli

How to build libdot

First, clone a copy of the libdot git repo by running:

git clone

Enter the libdot directory and install the Node dependencies, this time without specifying a global install:

cd libdot && npm install

Then, to get a complete, minified version of libdot.min.js, type the following:


The built, minified version of libdot will be put in the dist/ subdirectory.


If you have questions, the best place to ask is the chromium-hterm google group