[Statsig Adpater] migrate from statsig-node-lite to @statsig/serverless-client
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 622
- Forks
- 87
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 14
Description
We use the Flag SDK in our NextJS app with the Statsig adapter and the Vercel Edge integration. We tried to setup Statsig session replays but it did not work when bootstraping server side with the instance provided by the adapter because of some missing fields. It appears the package used by the adapter (statsig-node-lite) is no longer maintained and will be deprecated in favor of @statsig/serverless-client (cf screenshot).
We could replace statsig-node-lite and statsig-node-vercel by @statsig/vercel-edge to make sure @flags-sdk/statsig supports the latest Statsig features.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Statsig adapter and its dependency manifests, then trace how statsig-node-lite and statsig-node-vercel provide the Vercel Edge integration. Compare those uses with @statsig/serverless-client and @statsig/vercel-edge, and verify that server-side bootstrapping still exposes the fields needed for session replays. Done means the adapter uses the maintained packages without regressing the documented Next.js Edge integration.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- cloud, tooling
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100