Replies: 1 comment
-
Hey @MichaelDeBoey and @ryanflorence. What do you think about this? |
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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey!
Big monorepo makes development complicated. Each dependency need to watch and rebuild, then remix should catch the change and rebuild. Having watcher for every package increases fs usage and makes battery life shorter.
To solve this we can provide sources as entry points instead of compiled code. Though then distributing packages on rpm gets more complicated because need to prepare separate package.json on prepublish hooks.
The best solution I found is using node exports conditions. For example vite allows to tweak default resolver and change conditions. So we can add "source" condition and tweak config.
Remix though supports this trick only for server setup and no way to tweak client bundle resolver. clientConditions and clientMainFields similar to server variants would do the trick and make monorepo development super smooth.
See example how we use it in webstudio
https://github.com/webstudio-is/webstudio-builder/blob/3a16cb18216ee6010bc42b2afe880adcb6fa2b3b/packages/storybook-config/index.js#L11-L18
Beta Was this translation helpful? Give feedback.
All reactions