failed build after updating to next 13.5.1

[loudmu]

No description provided.

[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 @loudmu, could you share details about the failed build? What error are you seeing?

[angeloashmore]

Duplicate of #84.

[loudmu]

I updated to @prismicio/next": "^1.3.5" and I still have the same failed build problem. when remove Preview/route.ts and exit-preview./route the build works .

package.txt
prismic build.txt

[jere-co]

I updated to @prismicio/next": "^1.3.5" and I still have the same failed build problem. when remove Preview/route.ts and exit-preview./route the build works .

package.txt prismic build.txt

Make sure to return:

-  await redirectToPreviewURL({ client, request });
+  return await redirectToPreviewURL({ client, request });

[loudmu]

the problem occurs only in windows10 environment . I moved my dev environment to Ubuntu and everything works perfectly.

[angeloashmore]

@loudmu Could you confirm that you have the latest @prismicio/next by deleting your node_modules folder and re-installing?

[loudmu]

problem solved after updating to next 13.5.3!