npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

node-pre-gyp-init

v1.2.1

Published

Resolves a native binding at runtime and builds it if doesn't exist

Downloads

4,142

Readme

node-pre-gyp-init

NPM Version NPM Downloads Deps Dev Deps

node-pre-gyp-init complements node-pre-gyp by providing runtime native binding resolution and automatic native module compilation.

In other words, you can safely change your Node.js version and if you are missing the appropriate compiled native binary, it will asynchronously invoke node-pre-gyp to either download or compile the required binary.

Installation

npm install node-pre-gyp-init

Examples

If you are a native module author, one way to use node-pre-gyp-init is to call init() from all of your public JavaScript APIs. Since node-pre-gyp-init is async, your JavaScript API will also need to be async.

var init = require('node-pre-gyp-init');

module.exports.myNativeFunction = function (callback) {
    init(path.resolve(__dirname, './package.json'), function (err, bindingPath) {
		if (err) {
            return callback(err);
        }

		var binding = require(bindingPath);
        var result = binding.whatever();
        callback(null, result);
	});
};

If you are trying to use someone else's native module, then you can do something like:

var init = require('node-pre-gyp-init');
var modulePath = require.resolve('some-native-module');

init(path.resolve(modulePath, './package.json'), function (err, bindingPath) {
    if (err) {
        console.error(err);
        return;
    }

    var someNativeModule = require('some-native-module');
    someNativeModule.doNativeThings();
});

In the above example, node-pre-gyp-init is simply being used to make sure the native binding exists before requiring the actual native module.

API

init(pathToPackageJson, callback)

  • pathToPackageJson (string) - The path to the native module's package.json.
  • callback(err, bindingPath) (function) - A function to call after resolving the binding path.

Returns an EventEmitter where you can listen for the following events:

  • success - The native binding was found.

    Parameters:

    • bindingPath (string) - The path to the resolved native module.
  • error - Failed to install the pre-compiled binding or locate the binding after it was successfully compiled.

    Parameters:

    • err (Error) - The error details. If the error was because of a build error, then the return code is stored in err.code.
  • stdout and stderr - Output directly from the node-pre-gyp subprocess. This is handy if you need to debug what node-pre-gyp is doing.

    Parameters:

    • output (string) - The output from node-pre-gyp.

License

(The MIT License)

Copyright (c) 2016 Chris Barber

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.