@eppo/node-server-sdk
Advanced tools
Comparing version 0.2.0 to 0.3.0
{ | ||
"name": "@eppo/node-server-sdk", | ||
"version": "0.2.0", | ||
"version": "0.3.0", | ||
"description": "Eppo node server SDK", | ||
"main": "dist/index.js", | ||
"files": [ | ||
"/dist" | ||
], | ||
"typings": "dist/node-server-sdk.d.ts", | ||
@@ -7,0 +10,0 @@ "scripts": { |
@@ -20,2 +20,31 @@ # Eppo Server-Side SDK for Node.js | ||
**The client must be a singleton**. The client instance stores assignment configurations in memory. To avoid inconsistent assignment results, the same client instance should be reused across requests. Invoke the `init` method once at application startup to generate the client. | ||
**The client must be a singleton**. The client instance stores assignment configurations in memory. To avoid inconsistent assignment results, the same client instance should be reused across requests. Invoke the `init` method once at application startup to generate the client. | ||
## Contributing | ||
### Pull Requests | ||
Create a new branch off of `main` and submit a PR. In the PR, update the `Unreleased` section of the changelog with a description of your change: | ||
``` | ||
## Unreleased | ||
* Brief description of your change | ||
``` | ||
Do not change the package version in the PR. | ||
### Release Process | ||
A release may include changes from multiple pull requests. Only the package maintainers have access to publish releases. | ||
1) Checkout the `main` branch and pull the latest changes | ||
2) Bump the package version: `npm version [major | minor | patch]`. | ||
- Follow [Semver guidelines](https://semver.org/) when choosing major | minor | patch | ||
3) Update CHANGELOG.md with the list of changes that have occurred since the last release. Commit the version bump and CHANGELOG updates to the main branch. Example: | ||
4) `npm login` - enter your credentials | ||
5) `npm publish`. (You can also do `npm publish --dryrun` to test) |
50
47586
72
592