Releases: opennextjs/opennextjs-cloudflare
@opennextjs/[email protected]
Patch Changes
-
1b3a972: Dump ESBuild metadata to
handler.mjs.meta.json
The ESBuild metadata are written to a file alongside
handler.mjs
in.open-next/server-functions/default/...
-
5c90521: refactor: Make the list of optional dependencies configurable
-
67acb2f: fix build issues with
@opentelemetry
By using the pre-compiled library provided by Next.
-
3ed6cd1: fix: syntax error
@opennextjs/[email protected]
Patch Changes
-
1a2b815: fix: make sure that the
initOpenNextCloudflareForDev()
logic runs only onceCurrently calling
initOpenNextCloudflareForDev()
in the Next.js config file causes
this initialization logic to run twice, consuming more resources and causing extra
noise in the terminal logs, this change makes sure that the initialization logic
is run only once instead
@opennextjs/[email protected]
Minor Changes
-
8de2c04: introduce new
initOpenNextCloudflareForDev
utility and makegetCloudflareContext
synchronousthis change introduces a new
initOpenNextCloudflareForDev
function that must called in the Next.js config file to integrate the Next.js dev server with the open-next Cloudflare adapter.Also makes
getCloudflareContext
synchronous.Additionally the
getCloudflareContext
can now work during local development (next dev
) in the edge runtime (including middlewares).Moving forward we'll recommend that all applications include the use of the
initOpenNextCloudflareForDev
utility in their config file (there is no downside in doing so and it only effect local development).Example:
// next.config.mjs import { initOpenNextCloudflareForDev } from "@opennextjs/cloudflare"; initOpenNextCloudflareForDev(); /** @type {import('next').NextConfig} */ const nextConfig = {}; export default nextConfig;
Patch Changes
-
4ec334a: fix: @vercel/og failing due to using the node version.
Patches usage of the @vercel/og library to require the edge runtime version, and enables importing of the fallback font.
@opennextjs/[email protected]
@opennextjs/[email protected]
Patch Changes
- 67fafeb: fix top level awaits not working in middlewares by bumping the
@opennextjs/aws
package
@opennextjs/[email protected]
Patch Changes
- 05ee8d4: fix: invalid paths in windows bundles.
@opennextjs/[email protected]
@opennextjs/[email protected]
Patch Changes
-
9ab86d4: fix: host not included in route handler urls
Next.js was unable to re-construct the correct URLs for the request in a route handler due to being unable to retrieve the hostname. This was due to the internal Next.js option
trustHostHeader
being disabled in OpenNext when there is external middleware - this option is needed for the Next.js server in our environment.
@opennextjs/[email protected]
@opennextjs/[email protected]
Patch Changes
-
d488d86: fix: exclude
.env.local
files fortest
modeAligns with the Next.js behavior of not extracting variables from the
.env.local
file in test environments. -
0ee77b2: fix the city header encoding
By pulling opennextjs/opennextjs-aws#688
-
4b6a50b: check and create a
wrangler.json
file for the user in case awrangler.(toml|json|jsonc)
file is not already presentalso introduce a new
--skipWranglerConfigCheck
cli flag and aSKIP_WRANGLER_CONFIG_CHECK
environment variable that allows users to opt out of the above check (since developers might
want to use custom locations for their config files) -
7654867: bump
"@opennextjs/aws
dependency tohttps://pkg.pr.new/@opennextjs/aws@686