Node.js libgit2 asynchronous native bindings
Node bindings to the libgit2 project.
![Build Status] (https://travis-ci.org/nodegit/nodegit.svg) ![Build status] (https://ci.appveyor.com/api/projects/status/e5a5q75l9yfhnfv2?svg=true) ![Dependency Status] (https://david-dm.org/nodegit/nodegit.svg)
NodeGit will work on most systems out-of-the-box without any native dependencies.
npm install nodegit
If you encounter problems while installing, you should try the Building from source instructions below.
If you wish to help contribute to nodegit it is useful to build locally.
# Fetch this project.git clone git://github.com/nodegit/nodegit.git# Enter the repository.cd nodegit# Installs the template engine, run the code generation script, and build.npm install
If you encounter errors, you most likely have not configured the dependencies correctly.
In order to do so, follow these steps:
BUILD_ONLY=true npm install, or
BUILD_ONLY=true npm link .if you are into it
rm -rf build/Release
node-gyp configure --debug
node-gyp build --debug
Using APT in Ubuntu:
sudo apt-get install build-essential
Using Pacman in Arch Linux:
sudo pacman -S base-devel
You may have to add a build flag to the installation process to successfully install. Try first without, if the build fails, try again with the flag.
Allegedly the order in which you install Visual Studio could trigger this error.
npm install nodegit --msvs_version=2013# Or whatever version you've installed.
var clone = require"./"Cloneclone;// Clone a given repository into a specific folder.clone"" "tmp" null// Look up this known commit.then// Use a known commit sha from this repository.return repogetCommit"59b20b8d5c6ff8d09518454d4dd8b7b30f095ab5";// Look up a specific file within that commit.thenreturn commitgetEntry"README.md";// Get the blob contents from the file.then// Patch the blob to contain a reference to the entry.return entrygetBlobthenblobentry = entry;return blob;;// Display information about the blob.then// Show the name, sha, and filesize in byes.console.logblobentryname + blobentrysha + blobsize + "b";// Show a spacer.console.logArray72join"=" + "\n\n";// Show the entire file.console.logStringblob;catch console.logerr; ;
var open = require"nodegit"Repositoryopen;// Open the repository directory.open"tmp"// Open the master branch.thenreturn repogetMasterCommit;// Display information about commits on master.then// Create a new history event emitter.var history = firstCommitOnMasterhistory;// Create a counter to only show up to 9 entries.var count = 0;// Listen for commit events from the history.historyon"commit"// Disregard commits past 9.if ++count >= 9return;// Show the commit sha.console.log"commit " + commitsha;// Store the author object.var author = commitauthor;// Display author information.console.log"Author:\t" + authorname + " <" authoremail + ">";// Show the commit date.console.log"Date:\t" + commitdate;// Give some space and show the message.console.log"\n " + commitmessage;;// Start emitting events.historystart;;
You will need to build locally before running the tests. See above.
The bump from 0.1.4 to 0.2.0 was a big one. Many things changed, see here: https://github.com/nodegit/nodegit/compare/refs/tags/0.1.4...0.2.0
This update is wholly and entirely a breaking one, and older versions won't be maintained. For the purpose of migration, perhaps the biggest point to make is that async methods can now use promises, rather than just taking callbacks. Additionally, lots of method and property names have changed.
A common issue is with nodegit not functioning properly inside of
node-webkit applications. Because nodegit
is a native module, it has to be rebuilt for node-webkit using
nw-gyp. By default, nodegit will look in the root package's package.json for an
engines property, and within look for a
node-webkit property that holds a specific version of node-webkit. The value of this property is what will get passed as the
--target argument to
Currently, support for node-webkit is limited, although we intend to support it better in the future.