-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(statsig-adapter): Move Edge Config to peer deps, more consistent api key naming #43
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
New, updated, and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/[email protected] |
"peerDependencies": { | ||
"@vercel/edge-config": "~1.2.0", | ||
"statsig-node-vercel": "~0.4.0" | ||
}, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can further add this to mark the dependencies as optional
"peerDependenciesMeta": {
"@vercel/edge-config": {
"optional": true
},
"statsig-node-vercel": {
"optional": true
}
},
This way people not using Edge Config won't get warnings
3f9ef69
to
0dd8420
Compare
…), add origin, add exposure logging option
…ntation of the Statsig adapter
Overview
Statsig has
client | server | console
api keys. We can shore up the naming withstatsig
,[type]
, andapi key
. Use this convention across the adapter.Move Edge Config related dependencies to peer dependencies and dynamically import them when used, so that the flags SDK can be used without including Vercel if it's not needed.
Constrain the package.json requests to the major version, and let the app pin versions if desired