Replies: 1 comment
-
@jam-fran What we've done with our monorepo setup is we have a Storyblok instance that we run in the UI (which uses Vite) and that uses the plugin to auto-update the spritesheet which is registered in the package.json exports field and then consumed by other apps, I think it would maybe even be possible to register the path as "../../path" and have it listen to the ui but I haven't tried that to be honest |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Before I start shoutout to @AlemTuzlak for this very handy package!
This might be an obvious question, but I'm having trouble wrapping my mind around the best way to use this plugin in a monorepo.
For example, I'd like to have my icons in my internal "ui" package. But my ui package isn't compiled, that's handled by the apps within my monorepo that consume it (e.g. a remix app). So my ui package doesn't use vite, of course.
That may mean that this isn't the right solutoin for that use case, but I'm wondering if maybe the parent app can utilize this package, or if there's some other workaround given those constraints. Any ideas would be very much appreciated!
Beta Was this translation helpful? Give feedback.
All reactions