-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Build fails when using vite-imagetools plugin due to assets already existing in build/client #9498
Comments
I can verify the bug 😇 same on my side. As soon as I include the same image twice, remix build is failing. x Build failed in 270ms
Error: [remix] dest already exists.
at /Users/…/node_modules/fs-extra/lib/move/move.js:51:31
at /Users/…/node_modules/universalify/index.js:21:38 {
code: 'PLUGIN_ERROR',
plugin: 'remix',
hook: 'writeBundle'
} remix packages @2.9.2 The issues are the following:
OR
|
I can confirm that this bug was introduced in Remix version 2.9.2 likely with #9305 Here is the working reproduction https://github.com/alexandercarls/repro-imagetools with pinned version of |
Any news on this topic? We're still not able to update remix :/ |
Have the same issue currently. |
Adding { eager: true } to the import.meta.glob removed the error for me. Never investigated beyond that. |
Fixed by #9901. Once this is out in a nightly release, feel free to give it a try and report back. |
I get the following error when building Remix.
It seems that there is a build step where
build/server/assets
are moved over tobuild/client/assets
, but the images already exist there and the build fails due to the wayfs-extra/lib/move/move.js
behaves.I am using
vite-imagetools
which causes the assets to already exist inbuild/client/assets
.When calling directly
vite build
everything works. So to me it seems that Remix should do a better job at moving the files frombuild/server/assets
tobuild/client/assets
and not fail.The text was updated successfully, but these errors were encountered: