Qt bindings for Node.js

Usage no npm install needed!

<script type="module">
  import nodeQt from '';



Node-Qt provides native bindings to the Qt library as a Node.js addon. The focus is on graphics and audio bindings; there is no need to duplicate the functionality of the Node API and its modules.

We try to follow Qt's API as closely as possible, but sometimes quirks are inevitable (for example, virtual methods that handle events are translated into callback setters). See the header files in src/ for a list of available bindings, and comments in .cc files for possible API differences.

Supported platforms: Mac OS X | Windows | Linux

Hello world

var qt = require('node-qt'),
    app = new qt.QApplication,
    window = new qt.QWidget;

// Prevent objects from being GC'd = app;
global.window = window;

// Quirk: the virtual method paintEvent() is mapped into a callback setter
window.paintEvent(function() {
  var p = new qt.QPainter();
  p.drawText(20, 30, 'hello node, hello qt');

window.resize(300, 150);;

// Join Node's event loop
setInterval(app.processEvents, 0);

Getting started

From your project directory, run (see below for requirements):

$ npm install node-qt

This will download and build the latest release of Node-Qt in node_modules/. Then create a new file, say helloworld.js, copy the example above and run Node as usual:

$ node helloworld

See the examples/ directory for other simple use cases.


Node-Qt was designed to build seamlessly on a standard development box. The necessary platform-dependent Qt binaries are bundled with the module (due to heterogeneous dependencies, Linux is an exception).

  • Mac: Python, Make, and GCC.
  • Windows: Python and MSVC++ (either free or commercial).
  • Linux: Python, Make, GCC, and Qt 4.7+. To install Qt on Ubuntu: $ sudo apt-get install pkg-config qt-sdk.

Node-Qt has been tested with Node 0.6.x.


Building and testing

To download and build the development version:

$ git clone git://
$ cd node-qt
$ npm install

To run the unit tests:

$ node make test

(Ignore the image regression errors - they are based on snapshots that are platform- and backend-dependent).

Creating new bindings

Please provide a test case for every new binding added. See test/ for examples of unit tests.

Binding to new classes

  1. Create your files (e.g. qclass.h, from the provided templates src/template.h, src/
  2. qclass.*: search and replace all occurrences of __Template__, __TEMPLATE__, and __template__ with the corresponding class name
  3. node-qt.gyp: Add to sources list
  4. Include qclass.h
  5. Add QClass::Initialize() to Initialize()

Binding to new methods

  1. qclass.h: Declare static method as per Example() method in template.h
  2. Implement method as per Example() in
  3. Expose method to JavaScript via tpl->PrototypeTemplate() call in Initialize(). Again see

Common errors

This is a list of common errors when experimenting with Node addons, and their possible solutions:

"Out of memory"

name in NODE_MODULE(name, ...) does not match target name?

"Unable to load shared library"

(v8 object)->Set() called to register a method, but method implementation is missing?

"Segmentation fault"

Tough luck :) Did you forget to new a wrapped object?