Any way to apply the `common.js` to one of the entry files?

I'm using Factor-Bundle with Browserify to generate multiple partial bundles and a larger `common.js` file with all of the common requirements. However, one of the partial bundles corresponds to my main entrypoint, `main.js` which I would actually like to contain all of `common.js` so that I have one main file with all the common JS *and* the main contents of my app, and then the other partial bundles correspond to sub-apps.

To clarify, I am trying to go from these entry points:
- `main.js`
- `sub-app1.js`
- `sub-app2.js`

to this:

- `main.js` (INCLUDING ALL COMMON REQUIREMENTS)
- `sub-app1.js` (only code and require()s unique to sub-app1)
- `sub-app2.js` (only code and require()s unique to sub-app2)

But Factor-Bundle gives me:

- `common.js` // <- can I merge this with main.js somehow???
- `main.js`
- `sub-app1.js` //good
- `sub-app2.js` //good

Unless there's some hidden option in Browserify or Factor-Bundle to generate them how I want, my next guess is there might be some Browserify function that would simply let me merge two generated packages back into one? I can't simply `browserify.bundle(common.js, main.js)` after the fact because those bundled files are in different locations and I get errors that it can't locate the relative file paths anymore.

Any ideas?

Commencez par lire le comportement de bundling de Factor-Bundle et Browserify pour les fichiers d’entrée main.js, sub-app1.js et sub-app2.js, en vous concentrant sur la manière dont common.js est généré. Déterminez si la sortie demandée peut être prise en charge sans rebundler les fichiers générés ; c’est terminé lorsque main.js inclut les requirements communs tandis que les bundles des sous-applications ne conservent que leur code spécifique.

Rédigé par le modèle d'indexation à partir du texte de l'issue.