Suppress child bundle when using multiple bundlers

[blujedis]

❔ Question

Is there a way via API to limit output of child bundles when building multiple bundles concurrently?

🔦 Context

Server side React environment requires building both server and client bundles. Now I've noticed a bug that has been currently tagged here #1903 which I also ran into.

What I'm noticing is, in my case when importing my "App" component for the server.tsx file is that I also get the corresponding .css file. This is because "App.tsx" imports a stylesheet.

This is NOT desirable as client.tsx has already bundled those assets.

So again the question is, is there a way to suppress this behavior?

💻 Code Sample

Here's how I'm iterating the multiple bundlers.

async function asyncForEach(array, cb) {
  for (let index = 0; index < array.length; index++) {
    await cb(array[index], index, array);
  }
}

// NOTE: "this.bundlers" is simply a map that's storing bundlers by name.

async run(watch: boolean = true) {

    await asyncForEach(['server', 'client'], async (k) => {
      const bundler = this.bundlers[k];
      bundler.options.watch = watch;
      await bundler.bundle();
    });

}

🌍 Your Environment

Software	Version(s)
Parcel	1.10.3
Node	8.11.4
npm/Yarn	6.4.1
OS	Mac OS 10.14

[peanutbother]

I think it could be possible by using code splitting.
For your server side you would reference css dependencies to an empty module or file while on client side code you would use the regular source codes.

in your package.json you would put something like this

"browser": {
    "./src/shared/resourceStub": "./src/shared/actualResource"
  },

You can find more information about code splitting here

[blujedis]

@peanutbother not using package.json I'm bundling via Parcel's API.

Yes I could use a dynamic import but seems to me there should be a way in the API to filter child bundles/assets.

Well at least that's my opinion, but yes I could use a dynamic import makes sense.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs.