SDK for using IronCore Labs from your NodeJS server side applications. Read our documentation for further information about how to integrate this library into your server side application. Also check out the integration directory for an example of consuming this library.
| Node 16 | Node 18 | Node 20 | |
|---|---|---|---|
| Linux x64 glibc | ✓ | ✓ | ✓ |
| Linux x64 musl-libc | ✓ | ✓ | ✓ |
| Linux arm64 glibc | ✓ | ✓ | ✓ |
| Linux arm64 musl-libc | ✓ | ✓ | ✓ |
| OSX x64 | ✓ | ✓ | ✓ |
| OSX arm64 | ✓ | ✓ | ✓ |
| Windows x64 | ✓ | ✓ | ✓ |
npm install @ironcorelabs/ironnode
This SDK relies on our recrypt-node-binding Node addon library. This library is distributed as a binary which is specific to both an architecture (OSX/Linux/Windows) and Node version (10/12). When you NPM install this SDK it will automatically determine the proper binary to pull down into your node_modules directory based on your architecture and Node version.
This means that you'll need to make sure that the machine that runs npm install to install this library is the architecture/Node version where the code will run. This library will not work if you run npm install on an OSX machine and move the node_modules directory over to a Linux machine, for example.
If the machine you run npm install on is not one of the supported architectures you will get an install failure. If there's an architecture or Node version that you'd like supported that isn't yet available, open a new issue and we'll look into adding support for it.
This library contains a TypeScript definitions file which shows the available classes and methods for this SDK.
In order to run the integration tests for this repo you need to have an IronCore Project, Segment, and Service Key to use. If you haven't yet, sign up for an account and create a set of those to use for testing this library.
Once you have all three items configured, do the following:
- Copy your Service Key
private.keyfile into theintegrationdirectory. - Create a
project.jsonfile in theintegrationdirectory with the following JSON form
{
"projectId": numeric project ID,
"segmentId": string segment ID,
"serviceKeyId": numeric service key ID,
}
Once you have your Service Key private key and config file setup, you can run the yarn start command to kick off an interactive CLI tool. This tool will first let you pick a user operation, either verify, create, or generate device keys. You can verify existing users or create new users from this menu. Before any SDK operations are allowed to run you must generate local device keys. When you pick this option and the keys are generated, they will be stored in a .device.json file in the integration directory. Subsequent CLI runs will ask if you want to use those local device keys.
This repo uses NPM scripts in order to run all tests and linting. You can run both the unit tests and linting together by running yarn test.
TSLint is used to run linting on all source code. In addition this repo has a Prettier configuration to auto-format source code upon save. Prettier should be configured within your IDE before contributing to this project.
yarn run lint
This repo uses Jest for all unit testing.
yarn run unit
To run a subset of the tests you can use the -t option of Jest to only run tests whose name matches the provided value
yarn run unit -t group
Copyright (c) 2020 IronCore Labs, Inc. All rights reserved.