Replies: 2 comments 1 reply
-
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. |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't know if this is the right way to do it but what I did was create a separate
|
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My Tubrorepo structure has a web-app that uses Vite to run and a shared UI from the package folder like this:
The shared UI has a StyledComponent that imports an SVG and use it as a background (just an example, so not the full component):
The SVG file will end up in the dist of
shared-ui
but my Vite app will never includeSomeSvg.svg
in the public folder and therefore allow the component to fetch the SVGs as a background image. If I copy the svg files to the public folder in my web-app everything will work.Is there a way to build packages and basically say "these are public assets and should be included in the build as such"?
Thanks 🙏
Beta Was this translation helpful? Give feedback.
All reactions