# Separate theme (as dependency), build artifacts

**URL:** https://discourse.roots.io/t/separate-theme-as-dependency-build-artifacts/10324
**Category:** sage
**Created:** 2017-08-30T15:24:38Z
**Posts:** 2

## Post 1 by @strarsis — 2017-08-30T15:24:38Z

I want to share a Sage based theme between two (or more) Bedrock based sites.  
The Sage theme got proper composer.json and tags so composer can pull it like any other plugin dependency.

However - how to handle the build artifacts? Should I do dirty commits with the build artifacts into an extra branch? I don’t think composer should install the node packages and run the build script by itself - so the build artifacts should properly already available as static files.

---

## Post 2 by @ned — 2017-08-30T15:58:41Z

Related to [Controller doesn't work when installing Sage-based theme via Composer](https://discourse.roots.io/t/controller-doesnt-work-when-installing-sage-based-theme-via-composer/10272/10) (currently Controller doesn’t work when installing a Sage-based theme via Composer).