2acb53bd30
**What's the problem this PR addresses?** A decent amount of the examples don't have a `name` field in `package.json` that matches their folder name, meaning they either lack a name or the names are duplicated. I was testing Yarn 2 workspaces using the entire examples directory and needed to get rid of the duplicates. **How did you fix it?** Updated the names to match the names of their folders |
||
---|---|---|
.. | ||
components | ||
pages | ||
utils | ||
.gitignore | ||
package.json | ||
README.md |
Tesfy Example
Tesfy allows you to create unlimited A/B Tests and Feature Flags for free using a web app or by your self.
This example shows how to integrate react-tesfy in Next.js.
To use Tesfy there are only two mandatory things needed. A userId
and a configuration file known as datafile
. In the _app.js
you will notice that those are being get.
The userId
must uniquely identify a user even if not logged in, for that reason a uuid is created and stored in a cookie so the next time a page is requested a new userId
won't be created, instead the cookie one will be used.
The datafile
is just a json
that defines the configuration of the experiments and features available. It must be fetched from Tesfy CDN or from your own servers at least everytime a request is performed, later on this configuration could also be fetched if wanted (e.g. during page transitions).
Deploy your own
Deploy the example using Vercel:
How to use
Execute create-next-app
with npm or Yarn to bootstrap the example:
npx create-next-app --example with-tesfy with-tesfy-app
# or
yarn create next-app --example with-tesfy with-tesfy-app
Deploy it to the cloud with Vercel (Documentation).