Support separate client and server bundles #751
Labels
problem: stale
Issue has not been responded to in some time
solution: duplicate
This issue or pull request already exists
topic: multi-entry
Related to multi-entry support
Milestone
Current Behavior
Currently tsdx only generates one single bundle.
Desired Behavior
We are using tsdx for Blitz.js and we need separate client and server bundles. The Blitz package has (1) code that is isopmorphic and (2) code that only runs on the server.
Currently we have two separate packages to accomplish this but it's a huge mess for code organization because we can't organize code by feature. Code for a certain feature has to be separated in two separate packages. Instead we want all this code to be in a single package.
And then we want to be able to import a specific bundle, maybe like this:
Suggested Solution
I'm not sure the best way to do this, but I could image having a file structure like this:
Who does this impact? Who is this for?
Anyone writing packages that have different functionality on client vs server.
Describe alternatives you've considered
Custom rollup config which I don't know how to do 😅
Additional context
blitz-js/legacy-framework#928
The text was updated successfully, but these errors were encountered: