This makes it so the rest of the code within the example uses NEXT_PUBLIC_TURNKEY_API_BASE_URL instead of NEXT_PUBLIC_BASE_URL --> the readme and example local env use the former (which is more descriptive) and the code uses the latter causing some confusion
Summary & Motivation
How I Tested These Changes
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run pnpm changeset. pnpm changeset will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).
These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.
This makes it so the rest of the code within the example uses
NEXT_PUBLIC_TURNKEY_API_BASE_URL
instead ofNEXT_PUBLIC_BASE_URL
--> the readme and example local env use the former (which is more descriptive) and the code uses the latter causing some confusionSummary & Motivation
How I Tested These Changes
Did you add a changeset?
If updating one of our packages, you'll likely need to add a changeset to your PR. To do so, run
pnpm changeset
.pnpm changeset
will generate a file where you should write a human friendly message about the changes. Note how this (example) includes the package name (should be auto added by the command) along with the type of semver change (major.minor.patch) (which you should set).These changes will be used at release time to determine what packages to publish and how to bump their version. For more context see this comment.