This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@opennextjs/cloudflare@0.1.0
Minor Changes
87f4fb5: feat: configure kv binding name with env var
The Workers KV binding used in the Next.js cache handler can be given a custom name with the __OPENNEXT_KV_BINDING_NAME environment variable at build-time, instead of defaulting to NEXT_CACHE_WORKERS_KV.
The cache handler was retrieving it's KV instance as a static property on the class that was defined at some point during the execution of the Next.js server. This moves the retrieval of the KV instance to happen inside the constructor for the class, so that it is retrieved during instantiation instead.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@opennextjs/cloudflare@0.1.0
Minor Changes
87f4fb5: feat: configure kv binding name with env var
The Workers KV binding used in the Next.js cache handler can be given a custom name with the
__OPENNEXT_KV_BINDING_NAME
environment variable at build-time, instead of defaulting toNEXT_CACHE_WORKERS_KV
.Patch Changes
83abcfe: refactor: retrieve cache handler kv instance inside constructor
The cache handler was retrieving it's KV instance as a static property on the class that was defined at some point during the execution of the Next.js server. This moves the retrieval of the KV instance to happen inside the constructor for the class, so that it is retrieved during instantiation instead.