New in Koffi 2.0: koffi.resolve(), new in Koffi 2.2: koffi.offsetof()


The value returned by introspect() has changed in version 2.0 and in version 2.2.

In Koffi 1.x, it could only be used with struct types and returned the object passed to koffi.struct() with the member names and types.

Starting in Koffi 2.2, each record member is exposed as an object containing the name, the type and the offset within the record.

Consult the migration guide for more information.

Use koffi.introspect(type) to get detailed information about a type: name, primitive, size, alignment, members (record types), reference type (array, pointer) and length (array).

 1const FoobarType = koffi.struct('FoobarType', {
 2    a: 'int',
 3    b: 'char *',
 4    c: 'double'
 9// Expected result on 64-bit machines:
10// {
11//     name: 'FoobarType',
12//     primitive: 'Record',
13//     size: 24,
14//     alignment: 8,
15//     members: {
16//         a: { name: 'a', type: [External: 4b28a60], offset: 0 },
17//         b: { name: 'b', type: [External: 4b292e0], offset: 8 },
18//         c: { name: 'c', type: [External: 4b29260], offset: 16 }
19//     }
20// }

Koffi also exposes a few more utility functions to get a subset of this information:

  • koffi.sizeof(type) to get the size of a type

  • koffi.alignof(type) to get the alignment of a type

  • koffi.offsetof(type, member_name) to get the offset of a record member

  • koffi.resolve(type) to get the resolved type object from a type string

Just like before, you can refer to primitive types by their name or through koffi.types:

1// These two lines do the same:


New in Koffi 2.0

You can alias a type with koffi.alias(name, type). Aliased types are completely equivalent.


Memory usage#

For synchronous/normal calls, Koffi uses two preallocated memory blocks:

  • One to construct the C stack and assign registers, subsequently used by the platform-specific assembly code (1 MiB by default)

  • One to allocate strings and big objects/structs (2 MiB by default)

Unless very big strings or objects (at least more than one page of memory) are used, Koffi does not directly allocate any extra memory during calls or callbacks. However, please note that the JS engine (V8) might.

The size (in bytes) of these preallocated blocks can be changed. Use koffi.config() to get an object with the settings, and koffi.config(obj) to apply new settings.

1let config = koffi.config();

The same is true for asynchronous calls. When an asynchronous call is made, Koffi will allocate new blocks unless there is an unused (resident) set of blocks still available. Once the asynchronous call is finished, these blocks are freed if there are more than resident_async_pools sets of blocks left around.

There cannot be more than max_async_calls running at the same time.

Default settings#





1 MiB

Stack size for synchronous calls


2 MiB

Heap size for synchronous calls


256 kiB

Stack size for asynchronous calls


512 kiB

Heap size for asynchronous calls



Number of resident pools for asynchronous calls



Maximum number of ongoing asynchronous calls


64 MiB

Maximum size of Koffi types (for arrays and structs)

Usage statistics#

New in Koffi 2.3.2

You can use koffi.stats() to get a few statistics related to Koffi.

POSIX error codes#

New in Koffi 2.3.14

You can use koffi.errno() to get the current errno value, and koffi.errno(value) to change it.

The standard POSIX error codes are available in koffi.os.errno, as shown below:

 1const assert = require('assert');
 3// ES6 syntax: import koffi from 'koffi';
 4const koffi = require('koffi');
 6const lib = koffi.load('libc.so.6');
 8const close = lib.func('int close(int fd)');
11assert.equal(koffi.errno(), koffi.os.errno.EBADF);
13console.log('close() with invalid FD is POSIX compliant!');

Reset internal state#

New in Koffi 2.5.19

You can use koffi.reset() to clear some Koffi internal state such as:

  • Parser type names

  • Asynchronous function broker (useful to avoid false positive with jest --detectOpenHandles)

This function is mainly intended for test code, when you execute the same code over and over and you need to reuse type names.


Trying to use a function or a type that was initially defined before the reset is undefined behavior and will likely lead to a crash!