We don't have a Turborepo-native solution for this today and I don't know of anything in the JS/TS ecosystem that solves for this out-of-the-box. You can certainly write a Node.js script to spread your static assets around into your application's public directories prior to builds.

That said, I'd be interested in seeing if we could figure out a Turbo native solution for this.

Does this have any roadmap or idea yet?

No, we haven't spent time thinking about this, and it's not clear at this point that this is something that should be solved with Turborepo.

In general, folks who have a need for this should really be using a blob storage solution, persisting the assets outside of their Git repo. Static assets are large blobs, which degrade Git performance quickly.

Still, if you do insist on storing the assets in your Git repo, a bundler that handles static assets could be used to bundle to something Node.js can export from a package. Again, this goes against first principles, but you can still do it.

I see.. We are using private network when deploy the apps so the only option to host at aws s3 is not allowed. I am still finding another workaround

@AabhasDhaubanja

Can you show how your @repo/assets looks like?

The only problem on this is the difference between what is asset and what is on public, and how the bundler will treat this

https://stackoverflow.com/questions/44643041/do-i-store-image-assets-in-public-or-src-in-reactjs

And if you wanna put something on your public folder, let's say from your app (which calls your package) you could do:

declare module '@public/*' {
  const value: any;
  export default value;
}

and them:

import Image from '@public/image.png';

This will at least allow your inteliSense to work (LSP) and on build and dev no problems as well.

For build you gotta add this to your alias:

resolve: {
      alias: [
          {
             find: '@public',
             replacement: './public'
          },
      ]
},

Idk if it's the best solution, but it works well, what is public is used as it should, and the IDE adapts right to it.