[remix] dest already exists.

[eugeniobet]

          @danestves @robertjpayne Can you please confirm that v2.7.2 fixes your issue?

Originally posted by @markdalgleish in https://github.com/remix-run/remix/issues/8813#issuecomment-1957797735

Build error 'writeBundle' seems to be back with 2.9.2. Works up until 2.9.1.

[brophdawg11]

Can you share a reproduction?

[PuruVJ]

Can confirm! I started using vite-imagetools, copied the entire folder from public/images to app/assets/images. Then when I got the error I assumed it had to do with duplicated names in the final build, so I deleted the unused ones from both sides. Still didn't go away so downgrading to 2.9.1 fixed it.

Edit: I already started using unstable_defineLoader which was introduced in 2.9.2, hence I can't really downgrade anymore. Looking forward to a fix.

Edit 2: Commenting out imagetools completely fixes the issue, so imagetools is responsible to some degree

[eugeniobet]

I will investigate it further tomorrow although I'm not using vite-imagetools.

[alexandercarls]

This ticket is a duplicate of https://github.com/remix-run/remix/issues/9498. I've just came the the same conclusion that it works with 2.9.1 and posted a quick reproduction in my comment there.

[github-actions[bot]]

Thank you for opening this issue, and our apologies we haven't gotten around to it yet!

With the release of React Router v7 we are sun-setting continued development/maintenance on Remix v2. If you have not already upgraded to React Router v7, we recommend you do so. We've tried to make the upgrade process as smooth as possible with our Future Flags. We are now in the process of cleaning up outdated issues and pull requests to improve the overall hygiene of our repositories.

We plan to continue to address 2 types of issues in Remix v2:

• Bugs that pose security concerns
• Bugs that prevent upgrading to React Router v7

If you believe this issue meets one of those criteria, please respond or create a new issue.

For all other issues, ongoing maintenance will be happening in React Router v7, so:

• If this is a bug, please reopen this issue in that repo with a new minimal reproduction against v7
• If this is a feature request, please open a new Proposal Discussion in React Router, and if it gets enough community support it can be considered for implementation

If you have any questions you can always reach out on Discord. Thanks again for providing feedback and helping us make our framework even better!