v1.7.0 is not compatible with Next v14.x

[marvinbernd]

Versions

• @prismicio/next: v.1.7.1
• next: v14.2.3
• node: v20.10.0

Reproduction

When trying to run local environemnt I get the follwoing error:
Uncaught (in promise) Error: draftMode was called outside a request scope. Read more: https://nextjs.org/docs/messages/next-dynamic-api-wrong-context

Steps to Reproduce

1. Set up a Next.js project with v14.2.3.
2. Install @prismicio/next v1.7.0.
3. Run the project and trigger a route.
4. Observe the error in the console.

Expected Behavior

draftMode() should work as intended within the context of the request scope without throwing an error.

Actual Behavior

The error mentioned above is thrown, preventing the feature from functioning.

Possible Cause

The change on draftMode() from a sync to an async function in v1.7.0 is not compatible with Next v14.x

Workaround

Downgrading @prismicio/next to v1.6.x or an earlier compatible version resolves the issue.

Suggested Fix

v1.7.0 is a breaking change and should be a major version release.

[github-actions]

This issue has been labeled as a bug since it was created using the 🚨 Bug Report Template.

Hi there, thank you so much for the report!

Following our Maintenance Process, we will review your bug report and get back to you next Wednesday. To ensure a smooth review of your issue and avoid unnecessary delays, please make sure your issue includes the following:

• Information about your environment and packages you use (Node.js version, package names and their versions, etc.)
  Feel free to attach a copy of your package.json file.
• Any troubleshooting steps you already went through
• A minimal reproduction of the issue, and/or instructions on how to reproduce it

If you have identified the cause of the bug described in your report and know how to fix it, you're more than welcome to open a pull request address it. Check out our quick start guide for a simple contribution process.

If you think your issue is a question (not a bug) and would like quicker support, please close this issue and forward it to an appropriate section on our community forum: https://community.prismic.io

- The Prismic Open-Source Team

[angeloashmore]

Hi @marvinbernd, could you update to v1.7.1? The latest version, released in October, includes a compatibility fix for Next.js 15 and 14. You can find more details here: #98

I wasn't able to reproduce your error using v1.7.1 and a Next.js 14 app.

For context, v1.7.0 was released in September, before Next 15 was released.

[marvinbernd]

Hey @angeloashmore, I wasn't able to reproduce it in a clean project with v1.7.1 and Next 14.2.20.

But still in my project I get the error with v1.7.0 and v1.7.1. v1.5.0 and v1.6.0 works fine.