Update edge-dynamic-code-evaluation.mdx

[paul-vd]

Following the MiddlewareConfig typings, this is now named as unstable_allowDynamicGlobs

[ijjk]

Allow CI Workflow Run

• approve CI run for commit: 63acb86

Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer

[eps1lon]

We still parse it as unstable_allowDynamic not unstable_allowDynamicGlobs:

next.js/packages/next/src/build/analysis/get-page-static-info.ts

Lines 404 to 421 in 1e3a1cb

	if (config.unstable_allowDynamic) {
	result.unstable_allowDynamicGlobs = Array.isArray(
	config.unstable_allowDynamic
	)
	? config.unstable_allowDynamic
	: [config.unstable_allowDynamic]
	for (const glob of result.unstable_allowDynamicGlobs ?? []) {
	try {
	picomatch(glob)
	} catch (err) {
	throw new Error(
	`${pageFilePath} exported 'config.unstable_allowDynamic' contains invalid pattern '${glob}': ${
	(err as Error).message
	}`
	)
	}
	}
	}

Our tests also use unstable_allowDynamic not unstable_allowDynamicGlobs: https://github.com/vercel/next.js/blob/1e710ab73ce6b6ee896535ef0962956aac2e9649/test/integration/edge-runtime-configurable-guards/test/index.test.js

Is the MiddlewareConfig you linked reachable from usercode or do we document that this is the type you should export your config as?

[leerob]

Edit: nevermind

Missed other comment

[jerome-quere]

@eps1lon

Is the MiddlewareConfig you linked reachable from usercode or do we document that this is the type you should export your config as?

Not documented but reachable from usercode

import { MiddlewareConfig, NextRequest, NextResponse } from 'next/server'

"next": "14.2.2",

[elartix]

Hi folks, caught regression issue with unstable_allowDynamic feature in 14.2.x

#51401 (comment)

[leerob]

@elartix That appears to be solved with #73732.

As mentioned above, the config option is still unstable_allowDynamic – we do not document the type referenced here, which is used internally in Next.js. If we do end up exposing this type in the documentation as something you should use, we can revisit the naming here.