Full-featured event loop backed by epoll, kqueue, IOCP, event ports.
Asynchronous TCP and UDP sockets
Asynchronous DNS resolution
Asynchronous file and file system operations
File system events
ANSI escape code controlled TTY
IPC with socket sharing, using Unix domain sockets or named pipes (Windows)
High resolution clock
Threading and synchronization primitives
Starting with version 1.0.0 libuv follows the semantic versioning scheme. The API change and backwards compatibility rules are those indicated by SemVer. libuv will keep a stable ABI across major releases.
Official API documentation
Located in the docs/ subdirectory. It uses the Sphinx framework, which makes it possible to build the documentation in multiple formats.
Show different supported building options:
$ make help
Build documentation as HTML:
$ make html
Build documentation as man pages:
$ make man
Build documentation as ePub:
$ make epub
NOTE: Windows users need to use make.bat instead of plain 'make'.
Documentation can be browsed online here.
The tests and benchmarks also serve as API specification and usage examples.
- An Introduction to libuv — An overview of libuv with tutorials.
- LXJS 2012 talk — High-level introductory talk about libuv.
- libuv-dox — Documenting types and methods of libuv, mostly by reading uv.h.
- learnuv — Learn uv for fun and profit, a self guided workshop to libuv.
These resources are not handled by libuv maintainers and might be out of date. Please verify it before opening new issues.
Starting with libuv 1.7.0, binaries for Windows are also provided. This is to be considered EXPERIMENTAL.
Before verifying the git tags or signature files, importing the relevant keys is necessary. Key IDs are listed in the MAINTAINERS file, but are also available as git blob objects for easier use.
Importing a key the usual way:
$ gpg --keyserver pool.sks-keyservers.net \ --recv-keys AE9BC059
Importing a key from a git blob object:
$ git show pubkey-saghul | gpg --import
Git tags are signed with the developer's key, they can be verified as follows:
$ git verify-tag v1.6.1
Starting with libuv 1.7.0, the tarballs stored in the downloads site are signed and an accomanying signature file sit alongside each. Once both the release tarball and the signature file are downloaded, the file can be verified as follows:
$ gpg --verify libuv-1.7.0.tar.gz.sign
For GCC there are two build methods: via autotools or via GYP. GYP is a meta-build system which can generate MSVS, Makefile, and XCode backends. It is best used for integration into other projects.
To build with autotools:
$ sh autogen.sh $ ./configure $ make $ make check $ make install
To build with Visual Studio, launch a git shell (e.g. Cmd or PowerShell) and run vcbuild.bat which will checkout the GYP code into build/gyp and generate uv.sln as well as related project files.
To have GYP generate build script for another system, checkout GYP into the project tree manually:
$ git clone https://chromium.googlesource.com/external/gyp.git build/gyp
$ ./gyp_uv.py -f make $ make -C out
./gyp_uv.py -f make -Dtarget_arch=x32 to build [x32] binaries.
$ ./gyp_uv.py -f xcode $ xcodebuild -ARCHS="x86_64" -project uv.xcodeproj \ -configuration Release -target All
$ brew install --HEAD libuv
Note to OS X users:
Make sure that you specify the architecture you wish to build for in the "ARCHS" flag. You can specify more than one by delimiting with a space (e.g. "x86_64 i386").
$ source ./android-configure NDK_PATH gyp $ make -C out
Note for UNIX users: compile your project with
-D_FILE_OFFSET_BITS=64. GYP builds take care of that automatically.
To use ninja for build on ninja supported platforms, run:
$ ./gyp_uv.py -f ninja $ ninja -C out/Debug #for debug build OR $ ninja -C out/Release
$ ./gyp_uv.py -f make $ make -C out $ ./out/Debug/run-tests
Microsoft Windows operating systems since Windows XP SP2. It can be built with either Visual Studio or MinGW. Consider using Visual Studio Express 2010 or later if you do not have a full Visual Studio license.
Linux using the GCC toolchain.
OS X using the GCC or XCode toolchain.
Solaris 121 and later using GCC toolchain.
AIX 6 and later using GCC toolchain (see notes).
AIX support for filesystem events requires the non-default IBM
package to be installed. This package provides the AIX Event Infrastructure
that is detected by
describes the package in more detail.
AIX support for filesystem events is not compiled when building with
See the guidelines for contributing.