Yeah I agree.

I actually probably could use that modules from here by just loading all the bolt libraries earlier in the script. I'll do that as a short term fix.

But yeah I would like to see a base library that sits above framework but below kernel. We could move things like bolt.kernel.fp and other utils like Globals into it, leaving kernel as just the bolt kernel, not kernel+utilities.

Would you be against the name "base" as the sub-project?

On 29/06/2013, at 2:47 AM, markhibberd <notifications@github.com> wrote:

> In projects/script/command/build.js:
> 
> > @@ -192,6 +202,41 @@ module.exports = function (help_mode) {
> >      });
> >    };
> >  
> > +  // resolve a path like 'a.b.c.d' in a nested object scope
> This exists in kernel.util.Globals, but I am not sure if you are able to use it easily here or not.
> 
> This leads to a follow on question, which I am seriously considering splitting out a "tools" project that everything depends on. I don't want the kernel to be a dumping ground for utilities (which it currently is to some extent because it sits at the bottom). Thoughts?
> 
> —
> Reply to this email directly or view it on GitHub.