# On build folders from images directory are not shown in public folder. Sage 10.1.7

**URL:** https://discourse.roots.io/t/on-build-folders-from-images-directory-are-not-shown-in-public-folder-sage-10-1-7/23393
**Category:** sage
**Tags:** sage10
**Created:** 2022-06-20T18:30:35Z
**Posts:** 5

## Post 1 by @IceManLoneWolf — 2022-06-20T18:30:35Z

In Sage 10.0.0 the directories inside the images folder would be copied over to the public folder when running the build command, but now on Sage 10.1.7 when running yarn build the the .css, .js, .jpg, etc are all just in the root public directory.

I was wondering what the reason for this and if there was a simple fix to make it work the way it did before?

---

## Post 2 by @strarsis — 2022-06-20T18:55:25Z

You would use the asset-related functions of the Sage runtime in order to resolve those files from the manifest.

> **[Sage 10.x: Compiling Assets | Roots Documentation](https://docs.roots.io/sage/10.x/compiling-assets/#theme-assets)**
>
> Sage uses Bud to compile and optimize assets, and to provide a simple interface for doing so.

---

## Post 3 by @alwaysblank — 2022-06-20T19:29:33Z

I can’t speak to the reason, but this thread has a workaround: [Sage 10 + Bedrock | Image assets not found - #12 by alwaysblank](https://discourse.roots.io/t/sage-10-bedrock-image-assets-not-found/23224/12)

---

## Post 4 by @IceManLoneWolf — 2022-06-20T19:56:39Z

Nice. Thank you very much.

---

## Post 5 by @ben — 2022-06-20T20:30:18Z

This is a bug that will be resolved in Sage soon. Here’s another workaround: [Bug: Images in resources/images go into public root directly · Issue #3071 · roots/sage · GitHub](https://github.com/roots/sage/issues/3071#issuecomment-1160781474)