-
Notifications
You must be signed in to change notification settings - Fork 19
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
Bug(vite remix): EEXIST: file already exists, symlink "x" -> "y" #90
Comments
Can you try to narrow it down, or share a deployment URL with the issue? Without a reproduction, it's hard for me to say the cause. |
If I were to guess, I think you still have a |
There is no The deployment URL is: https://web-djdxk6xr2-pexip-engage.vercel.app It's deployed from a pnpm monorepo, and I did manage to get another smaller remix app building using the vite builder on vercel. However we're blocked on custom server file support there. I can look into deleting routes on a test branch to try and narrow it down |
Can you share the tree of your |
We're using the flat-routes package: Object.keys(__remixManifest.routes)
This is our complete `routes` tree in disk
|
If you could give me a reproduction repo then I can take a closer look. |
I'll try to trim down the project to pinpoint the issue and create a reproduction. Do you prefer to close this issue for now and I recreate an issue if I can find out more? Edit: |
Made a reproduction here, started from the vercel example: If you run it locally, you can see it working using the links in the root page. |
Thank you for the repro. I can reproduce the issue with this. We are investigating |
FWIW I've adjusted our routes from:
to:
Which leads to the same behaviour & avoids the build error. So we've been able to work around this issue. |
Encountering this as well, any findings? |
Hey,
I've been trying to migrate our remix app to use vite, but it seems to fail when deploying to vercel with a symlink error.
This is the only error log im getting when deploying. Im unsure how I can enable additional logging, or what is causing this error.
The application runs/builds fine with the current compiler.
I've tried with
"@vercel/remix": "2.8.1"
and"@vercel/remix": "2.8.1-patch.2"
The project is fairly large so hard to setup a reproduction as I have no clue what might be causing this.
The text was updated successfully, but these errors were encountered: