Where should images/videos go? Assets, public? somewhere else?

[emilyliquin]

Images in assets don't seem to load on deployment (but work in dev mode)

[guydav]

Currently seems to work -- if anyone has an example where putting assets in /assets doesn't work, can you share it?

[guydav]

Closing the issue for now until proven this is a problem -- if someone has a new example I'll happily debug it.

[rhezab]

Discussed with @emilyliquin and @guydav, we think the issue is when the image paths are string templates like bee-${i}.png. This is because of vite's static asset handling.

One solution is to put stuff in public/. Another solution is to do this.

Maybe add this to docs, at very least.

[guydav]

I think we should implement this design pattern in an example somewhere (after making sure it actually works) and reference in the documentation:

function getImageUrl(name) {
  return new URL(`./dir/${name}.png`, import.meta.url).href
}

@rhezab maybe we should try it with your experiment?

[rhezab]

Agree with Guy, I'll test this out and then add a note about this to the documentation if this works.

[gureckis]

I think @pclittle is about to go deep on exactly this issue because he has an experiment with a lot of videos that might need to preload so good chance to give him a recommendation and try it out!

[guydav]

I’m fairly sure the answer is assets with some preloading — happy to look at it with you @pclittleTypo’d from my iPhoneOn Apr 20, 2024, at 00:11, Todd Gureckis ***@***.***> wrote: I think @pclittle is about to go deep on exactly this issue because he has an experiment with a lot of videos that might need to preload so good chance to give him a recommendation and try it out! —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>