Comment 1 for bug 1552081

Hi Brian, yes it definitely would! Unfortunately this is far easier said than done - I know because I've said it too, and tried to get it done :)

In order to get these packages into the chroots automagically, they will need to be part of the chroot's framework, and at the moment that means: part of the phone image. Now node.js puts us in a difficult position as it is quite a volatile project that undergoes updates often, so it's very to justify one version to remain supported / stable in a particular framework / image.

This is what lead us to make the decision that node.js will not form part of the phone image, but instead will be shipped embedded in each scope (actually compiled into unity-js-scopes-launcher), allowing developers to update their version of the launcher, and hence node.js, as they release new editions of their scopes.

Now, that's not to say that we should not fix this process to be more transparent. I definitely agree with you there, I just wanted to give you some background :)

We will keep this bug around to monitor the issue, but I can't promise any swift action on this just yet unfortunately.

Thanks for reporting this though!