Replies: 2 comments
-
@crup That is an interesting feature actually 🤔 So you want the same codebase, but within, two different websites, one for mobile and one for tablet/desktop...? Seems quite complex, mhm. |
Beta Was this translation helpful? Give feedback.
-
@tigerabrodi If there are workarounds to support that feature, I will consider using Remix. I've already lost hopes from Next.js. |
Beta Was this translation helpful? Give feedback.
-
What is the new or updated feature that you are suggesting?
Can we get a support for configuring
entryClientFile
as an array instead of string to support multiple output bundles and serve them conditionally viaentryServerFile
?Why should this feature be included?
The idea behind having multiple client entry points is to support multiple outputs of a single app.
Let's say, I've an application where I want to serve a totally different website on mobile and I don't want to go with the responsive layout.
So I can have two entry points for the app:
entry.client.mobile.js
entry.client.desktop.js
Or maybe I want to separate out apps based on URLs like:
http://app.com/in
http://app.com/au
http://app.com/fr
So, these can be three different apps for three different countries.
Is it doable in Remix? Maybe via playing around with context in RemixServer?
Beta Was this translation helpful? Give feedback.
All reactions