Skip to content

fix(e2e): add await in middleware rewrite #855

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 6, 2025

Conversation

sommeeeer
Copy link
Contributor

This caused some issues running the E2E locally for me. If I ran the test with test.only() it would work. Not sure why it works in our GitHub Actions either. Anyhow, that line should be awaited.

Copy link

changeset-bot bot commented May 6, 2025

⚠️ No Changeset found

Latest commit: 31be8cd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@conico974 conico974 merged commit 7a5c018 into opennextjs:main May 6, 2025
1 check passed
@sommeeeer sommeeeer deleted the fix-e2e-mw-rewrite branch May 6, 2025 13:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants