Repository navigation
Remove the server.enhanceMiddleware deprecation warning - #2091
Merged
Merged
Conversation
Stop logging a deprecation warning when `server.enhanceMiddleware` is set. The option stays documented as deprecated in favor of `server.unstable_middleware`, `server.unstable_priorityMiddleware` and `server.unstable_onServerCreated`. Expo CLI still sets it itself, so every Expo user sees the warning without being able to act on it. The `defaultEnhanceMiddleware` sentinel only existed so the warning could tell the default apart from a user value, so it goes too. The default is an inline identity function again. Follow-up to #2031. Changelog: [Internal]
meta-cla
Bot
added
the
CLA Signed
huntie
approved these changes
Oct 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Stop logging a deprecation warning when
server.enhanceMiddlewareis set. The config remains deprecated (as it has been for a long time), just removing the new/unreleased warning, which can't land in a patch release.Frameworks still set
enhanceMiddlware, so (eg) every Expo user sees the warning without being able to act on it.In general, we should only introduce a loud deprecation warning:
In this case recommending an unstable API (which we're certain to remove or rename) over a deprecated one isn't moving folks forward.
Follow-up to #2031, unreleased. I'd consider this blocking for a Metro patch release.
Changelog: [Internal]