Asset path broken for some assets

[sigma-andex]

I'm trying to deploy a remix app (2.6.0) to vercel, but for some reason the assets are deployed to /build/vercel/path0/_assets/ and /build/_assets/. Unfortunately though, some of the assets (some pngs, but not all) are only deployed to /build/vercel/path0/_assets/ and therefore not found on my website. I have no idea why this happens and why it is only some of the pngs but not all. I have them in /app/assets but also tried /public and next to the importing tsx file.

[EndangeredMassa]

@sigma-andex can you share an example of this happening? IT could be your current project or a trimmed down version that reproduces the issue?

[lifeiscontent]

I'm seeing something similar, I'm importing files from the root index path, and a few other pages under /platforms/example I'm seeing /platforms being prepended to the asset url path on the /platforms/example page

an example image path looks like: /app/assets/homepage/example.png

usage is as follows:

import imageUrl from '~/assets/homepage/example.png`

export default function Route() {
  return <img src={imageUrl} />
}

on the platform page the resolved url looks something like: /platforms/assets/homepage/example.png

I'm using the new vercelPreset for remix + vite

[lifeiscontent]

CC: @TooTallNate

[TooTallNate]

@lifeiscontent I can not reproduce. Can you share your repository?

[lifeiscontent]

@TooTallNate yep, I'll put something together in the next hour or so. Thanks!

[lifeiscontent]

@TooTallNate here you go: lifeiscontent/remix-vercel-deploy-issue#1 let me know if you need any more context, I'm also available via discord at lifeiscontent if you'd like to chat further. Thanks again!

[lifeiscontent]

@TooTallNate I actually ended up figuring this out, I guess with vite, url handling is a little bit different, if I add a / to the beginning of _vercel/image? path things work again. That being said, any chance you guys will be adding support for #65 or at the very least do you have any recommendations on the code I've provided in that PR to better utilize Vercel's image optimization service in a more DX friendly way?

[TooTallNate]

Ok cool, sounds like this one can be closed then.

That being said, any chance you guys will be adding support for #65 or at the very least do you have any recommendations on the code I've provided in that PR to better utilize Vercel's image optimization service in a more DX friendly way?

Yes, I would like to add support for this. Follow the original issue for updates.