Build process not triggering for sub components

[unoriginalscreenname]

I noticed something with the automated build and browser refresh. If i am working inside a sub-component, the build process will trigger and refresh the browser, but the changes will not take effect unless I make a change to the parent component that is being included in the public index file.

example... I am loading this layout component in the public index.htm:

FamousFramework.deploy('username:layout', 'HEAD', 'body');

inside layout, my node tree looks like this, loading two sub components:

<node id="layout">
    <component1></component1>
<component2></component2>
</node>

If i make changes to either of the subcomponents, the build process goes, but no changes are displayed in the browser. If i save the parent "layout" component, the changes take effect.

This might be the way it was intended to work. if so that is alright. it's just not the way i expected it to behave. Hope this is helpful.

[djgrant]

A temporary fix is to build all components on every change by adding --rebuildEverythingOnChange=yes to the "local-only-bootstrap": setting in the package.json.

You might want to clear some of the famous components you're not using out of components/famous to speed the build process up if you're doing that.

See #30

[matthewtoast]

We'll also be adding another option soon that will allow you to develop with respect to a single component (instead of everything you have in your components folder), which also really speeds up the rebuilds.