Replies: 1 comment
-
After going through the Remix source code it was actually very easy to achieve the above goal with no changes required to Remix itself. All it took was some manipulation of the result returned from Heres my app structure:
Heres my
|
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.
-
Given I have an app which contains a guest area (eg. public facing website) and a separate area for members (eg. forums), with a modular approach I could organise the code like in the example below, with
lib
containing any shared business logic:This could be configured in the
remix.config.js
like below:This would be really helpful for code organisation and also splitting out the required assets so that each module route only serves the JS and CSS thats required. For example I could do a separate Tailwind configuration and build for each module so that then no CSS is shared across modules, made even simpler with upcoming Tailwind changes tailwindlabs/tailwindcss#9504
Beta Was this translation helpful? Give feedback.
All reactions