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

@archwayhq/keyring-go

v0.2.1

Published

A Node.js native addon for the Cosmos Keyring Go library to store values using the OS keyring or the filesystem

Downloads

33

Readme

Node Keyring

A Node-API addon for the Cosmos Keyring Go library to store values using the OS keyring or the filesystem.

Project Design and Structure

The project uses the recommended tooling for NAPI projects:

Folder structure:

  • src/go: contains all go files
  • src/keyring.cc: exposes the C-bound native API to Node.js using C++
  • src/node import the keyring.cc exports to Javascript

Development

Requirements

You will be building native code, and therefore, a comprehensive number of requirements are needed:

node --version
npm --version
make --version
go --version
python --version

On Mac

Install the XCode Command Line Tools:

xcode-select --install

Which will install clang:

cc --version

On Linux

gcc --version

[!NOTE] Confirm that you have a relatively recent version of each of these dependencies.

Setup

npm install --ignore-scripts

You should use the --ignore-scripts flag to avoid running the install script.

Build

npm run build

The build process uses cgo to compile the Go module into a static C library and node-gyp to make the C++ addon available on Node.js via NAPI.

To avoid compiling the package on the user's machine, the script uses prebuildify to prebuild the binaries for specific platforms. All the prebuilt node binaries are bundled with the package inside the prebuilds folder.

When installing the package, the install script will check if a compatible prebuild is bundled for the current platform. If it is, it will be used instead of building from source.

Once the build completes, you should see the build folder in the repository root containing all NAPI-related files.

The npm run build script will automatically run the build.sh script to build the Go module to a C library before producing the prebuild binary.

[!NOTE] On macOS, it's possible to build for both architectures (x64 and arm64). For that, you will need to run npm run build:x64 and then npm run build:arm64. Be aware that you should execute run npm run build later. Otherwise, the generated binaries might not be compatible with your current platform.

Build the Go package to C using cgo

To build only the Go module for your current platform and architecture, run:

./build.sh

Once the build is complete, you should see the files keyring.h and keyring.a in the out folder.

Test

To run the bindings tests:

npm run test