npmpackage.info

Gathering detailed insights and metrics for configcat-node

Other packages similar to configcat-node

configcat-common

9.3.1

ConfigCat is a configuration as a service that lets you manage your features and configurations without actually deploying new code.

configcat-js

9.5.1

ConfigCat is a configuration as a service that lets you manage your features and configurations without actually deploying new code.

configcat-react

4.8.0

ConfigCat is a configuration as a service that lets you manage your features and configurations without actually deploying new code.

configcat-js-ssr

8.4.3

ConfigCat Feature Flags for Server Side Rendered apps like NuxtJS. Official ConfigCat SDK for Server Side Rendered to easily access feature flags.

Gathering detailed insights and metrics for configcat-node

configcat-node

ConfigCat SDK for Node.js. ConfigCat is a hosted feature flag service: https://configcat.com. Manage feature toggles across frontend, backend, mobile, desktop apps. Alternative to LaunchDarkly. Management app + feature flag SDKs.

11.3.1

MIT

TypeScript

26.84 kB

5,855,343 4.5

Installations

npm install configcat-node

Score

96.6

Supply Chain

99.5

Quality

83.5

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

0

Total

67

Closed

8

Merged

59

Issues

Open

0

Total

10

Closed

10

Releases

v11.3.1

Published on 06 Sept 2024

v11.3.0

Published on 21 Mar 2024

v11.2.0

Published on 16 Jan 2024

v11.1.0

Published on 09 Jan 2024

v11.0.0

Published on 24 Nov 2023

v10.1.1

Published on 04 Aug 2023

View all 69 releases

Developer

configcat

Developer Guide

BETA

Module System

CommonJS

Min. Node Version

>=14

Typescript Support

Yes

Node Version

14.21.3

NPM Version

6.14.18 Statistics

19 Stars

339 Commits

7 Forks

5 Watching

2 Branches

19 Contributors

Updated on 08 Oct 2024

Bundle Size

105.62 kB

Minified

26.84 kB

Minified + Gzipped

Bundlephobia

Languages

TypeScript (96.34%)

Shell (1.96%)

JavaScript (1.71%)

Total Downloads

Cumulative downloads

Total Downloads

5,855,343

Last day

1.3%

13,754

Compared to previous day

Last week

1.9%

70,198

Compared to previous week

Last month

15.7%

286,635

Compared to previous month

Last year

55.2%

2,728,296

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Versions

ConfigCat SDK for Node.js

https://configcat.com

ConfigCat SDK for Node.js provides easy integration for your application to ConfigCat.

ConfigCat is a feature flag and configuration management service that lets you separate releases from deployments. You can turn your features ON/OFF using ConfigCat Dashboard even after they are deployed. ConfigCat lets you target specific groups of users based on region, email or any other custom user attribute.

ConfigCat is a hosted feature flag service. Manage feature toggles across frontend, backend, mobile, desktop apps. Alternative to LaunchDarkly. Management app + feature flag SDKs.

License

Getting Started

1. Install and import package:

via NPM package:

1npm i configcat-node

1const configcat = require("configcat-node");

2. Go to the ConfigCat Dashboard to get your SDK Key:

SDK-KEY

3. Create a ConfigCat client instance:

1const configCatClient = configcat.getClient("#YOUR-SDK-KEY#");

You can acquire singleton client instances for your SDK keys using the getClient("<sdkKey>") factory function. (However, please keep in mind that subsequent calls to getClient() with the same SDK Key return a shared client instance, which was set up by the first call.)

4. Get your setting value:

The async/await way:

1const value = await configCatClient.getValueAsync('isMyAwesomeFeatureEnabled', false);
2
3if (value) {
4  do_the_new_thing();
5} else {
6  do_the_old_thing();
7}

or the Promise way:

1configCatClient.getValueAsync('isMyAwesomeFeatureEnabled', false)
2  .then((value) => {
3    if (value) {
4      do_the_new_thing();
5    } else {
6      do_the_old_thing();
7    }
8  });

Getting user specific setting values with Targeting

Using this feature, you will be able to get different setting values for different users in your application by passing a User Object to getValueAsync().

Sample/Demo app

Polling Modes

The ConfigCat SDK supports 3 different polling mechanisms to acquire the setting values from ConfigCat. After latest setting values are downloaded, they are stored in the internal cache then all requests are served from there. Read more about Polling Modes and how to use them at ConfigCat Docs.

Need help?

https://configcat.com/support

Contributing

Contributions are welcome. For more info please read the Contribution Guideline.

About ConfigCat

Troubleshooting

Make sure you have the proper Node.js version installed

You might run into errors caused by the wrong version of Node.js. To make sure you are using the recommended Node.js version follow these steps.

Have nvm (Node Version Manager - https://github.com/nvm-sh/nvm ) installed:
Run nvm install. This will install the compatible version of Node.js.
Run nvm use. This will use the compatible version of Node.js.

No vulnerabilities found.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

License

Determines if the project has defined a license.

10

Packaging

Determines if the project is published as a package that others can easily download, install, easily update, and uninstall.

9

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

4

SAST

Determines if the project uses static code analysis.

1

Maintained

Determines if the project is "actively maintained".

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Fuzzing

Determines if the project uses fuzzing.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

Reason

dependency not pinned by hash detected -- score normalized to 0

Details

Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:70: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:72: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:27: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:29: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:46: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: GitHub-owned GitHubAction not pinned by hash: .github/workflows/node-ci.yml:47: update your workflow using https://app.stepsecurity.io/secureworkflow/configcat/node-sdk/node-ci.yml/master?enable=pin
Warn: containerImage not pinned by hash: samples/expresswithdocker/Dockerfile:1: pin your Docker image by updating node:10 to node:10@sha256:59531d2835edd5161c8f9512f9e095b1836f7a1fcb0ab73e005ec46047384911
Warn: npmCommand not pinned by hash: samples/expresswithdocker/Dockerfile:7
Warn: npmCommand not pinned by hash: deploy.sh:3
Warn: npmCommand not pinned by hash: update-samples.sh:4
Warn: npmCommand not pinned by hash: update-samples.sh:6
Warn: npmCommand not pinned by hash: update-samples.sh:8
Warn: npmCommand not pinned by hash: update-samples.sh:10
Warn: npmCommand not pinned by hash: update-samples.sh:12
Warn: npmCommand not pinned by hash: .github/workflows/node-ci.yml:35
Warn: npmCommand not pinned by hash: .github/workflows/node-ci.yml:53
Warn: npmCommand not pinned by hash: .github/workflows/node-ci.yml:54
Warn: npmCommand not pinned by hash: .github/workflows/node-ci.yml:79
Info: 0 out of 6 GitHub-owned GitHubAction dependencies pinned
Info: 0 out of 1 containerImage dependencies pinned
Info: 0 out of 11 npmCommand dependencies pinned

0

Security-Policy

Determines if the project has published a security policy.

0

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

Score

4.5

/10

Last Scanned on 2024-11-25

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More

Other packages similar to configcat-node

Other packages similar to configcat-node

configcat-node

Installations

Score

Pull Requests

0

67

8

59

Issues

0

10

10

Releases

Developer

Developer Guide

CommonJS

>=14

Yes

14.21.3

6.14.18

Statistics

Bundle Size

105.62 kB

26.84 kB

Languages

Total Downloads

5,855,343

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

Dev Dependencies

ConfigCat SDK for Node.js

Getting Started

1. Install and import package:

2. Go to the ConfigCat Dashboard to get your SDK Key:

3. Create a ConfigCat client instance:

4. Get your setting value:

Getting user specific setting values with Targeting

Sample/Demo app

Polling Modes

Need help?

Contributing

About ConfigCat

Troubleshooting

Make sure you have the proper Node.js version installed

10

10

10

10

9

4

1

0

0

0

0

0

0

4.5

/10