Error on Vercel deployment after building the remote cache locally

[andrewdoro]

What version of Turborepo are you using?

1.4.6

What package manager are you using / does the bug impact?

Yarn v1

What operating system are you using?

Windows

Describe the Bug

I built my repository on the local machine with remote caching enabled. When deploying to Vercel it caches succesfully, but it throws this error. This only happens when building on my local machine.

Expected Behavior

It shouldn't throw this error.

To Reproduce

yarn run build on my local machine deploy through vercel

[nathanhammond]

Okay, this is definitely an issue and we'd love to help you solve it. However, we're going to need a bit more help with reproduction so we can identify where precisely in the stack the problem is coming from.

Would it be possible to create reproduction steps from scratch, starting with npx create-turbo@latest all the way through deploy on Vercel, noting which caches were created where, and sharing the logs?

We're trying to identify where this is breaking down (build container, Next.js, or Turborepo).

You can also reach out to me in Discord and we can pair through the process of creating a reproduction. Let me know!

[andrewdoro]

I couldn't reproduce the error with the turbo examples, the problem looks to me related to turborepo because if I build the app on Vercel without the build cache it would work properly. Also might be related to this too one: https://github.com/vercel/vercel/discussions/7846 #

[nathanhammond]

If it's Turborepo in particular the issue is that it is caching a Windows-specific output that needs to be identified somehow.

The thing that stands out the most to me is that I saw mixed slashes in the error message. That makes it feel like it's a combination of all three of the systems.

[anthonyshew]

Closing due to inactivity! If you're still seeing this problem, please open up a fresh issue.