newbie chiming in... i upgraded to what looked like 3.6.0 earlier this week and ran into some firefoxos build issues - no module called shelljs or similar. fortunately the downgrade worked so i'm back in business.
has this issue been fixed in the current 3.6.0 candidate? (i'd like to upgrade to see whether a couple of other firefoxos issues have been sorted.) thanks for all the effort J On Thu, Sep 4, 2014 at 9:13 AM, Marcel Kinard <cmarc...@gmail.com> wrote: > That looks better. Thanks! > > On Sep 4, 2014, at 12:05 PM, Jesse <purplecabb...@gmail.com> wrote: > > > Okay, I think it's all cleaned up now ... sorry for the mess. > > > > @purplecabbage > > risingj.com > > > > > > On Thu, Sep 4, 2014 at 8:48 AM, Jesse <purplecabb...@gmail.com> wrote: > > > >> Oops, I'll sort this mess out now. > >> > >> @purplecabbage > >> risingj.com > >> > >> > >> On Thu, Sep 4, 2014 at 8:23 AM, Marcel Kinard <cmarc...@gmail.com> > wrote: > >> > >>> I'm looking at the 3.6.x branch of the wp8 repo, and seeing some > strange > >>> things: > >>> > >>> - the 3.6.0 tag is not at the head of the 3.6.x branch. It's not at the > >>> head of master either. It looks to be on a branch that has no head. > Doesn't > >>> make sense to me. > >>> - the addition of "bundledDependencies" to the package.json [f5453b9] > is > >>> not in the 3.6.x branch. But it is on that unnamed branch with the > 3.6.0 > >>> tag. > >>> - the removal of "-dev" from package.json [f6690f1] is not fully in the > >>> 3.6.x branch. It still says "-dev" in the description property. But it > is > >>> on that unnamed branch with the 3.6.0 tag. > >>> > >>> I'm thinking this should get cleaned up before packaging. I could > >>> cherry-pick the 2 commits from the unnamed branch to the 3.6.x branch > and > >>> visually inspect the resulting package.json, and move the 3.6.0 tag, > or is > >>> there a different approach that should be used here? > >>> > >>> I'll package up windows and android in the meantime. >
