@workos-inc/node
A Node wrapper for the WorkOS API

@workos-inc/node downloads @workos-inc/node version @workos-inc/node license

@workos-inc/node유사 패키지:
npm 다운로드 트렌드
3 년
🌟 @workos-inc/node의 README.md에 실시간 사용 차트를 표시하려면 아래 코드를 복사하세요.
## Usage Trend
[![Usage Trend of @workos-inc/node](https://npm-compare.com/img/npm-trend/THREE_YEARS/@workos-inc/node.png)](https://npm-compare.com/@workos-inc/node#timeRange=THREE_YEARS)
Cumulative GitHub Star Trend
🌟 @workos-inc/node의 README.md에 GitHub Stars 트렌드 차트를 표시하려면 아래 코드를 복사하세요.
## GitHub Stars Trend
[![GitHub Stars Trend of @workos-inc/node](https://npm-compare.com/img/github-trend/@workos-inc/node.png)](https://npm-compare.com/@workos-inc/node)
통계 세부사항
패키지
다운로드
Stars
크기
Issues
발행일
라이선스
@workos-inc/node406,783167924 kB419時間前MIT
@workos-inc/node의 README

WorkOS Node.js Library

npm Build Status

The WorkOS library for Node.js provides convenient access to the WorkOS API from applications written in server-side JavaScript.

Documentation

See the API Reference for Node.js usage examples.

Requirements

Node 16 or higher.

Installation

Install the package with:

npm i @workos-inc/node

Configuration

To use the library you must provide an API key, located in the WorkOS dashboard, as an environment variable WORKOS_API_KEY:

WORKOS_API_KEY="sk_1234"

Or, you can set it on your own before your application starts:

import { WorkOS } from '@workos-inc/node';

const workos = new WorkOS('sk_1234');

SDK Versioning

For our SDKs WorkOS follows a Semantic Versioning (SemVer) process where all releases will have a version X.Y.Z (like 1.0.0) pattern wherein Z would be a bug fix (e.g., 1.0.1), Y would be a minor release (1.1.0) and X would be a major release (2.0.0). We permit any breaking changes to only be released in major versions and strongly recommend reading changelogs before making any major version upgrades.

Beta Releases

WorkOS has features in Beta that can be accessed via Beta releases. We would love for you to try these and share feedback with us before these features reach general availability (GA). To install a Beta version, please follow the installation steps above using the Beta release version.

Note: there can be breaking changes between Beta versions. Therefore, we recommend pinning the package version to a specific version. This way you can install the same version each time without breaking changes unless you are intentionally looking for the latest Beta version.

We highly recommend keeping an eye on when the Beta feature you are interested in goes from Beta to stable so that you can move to using the stable version.

More Information