There was a major leak in the SDK which has been fixed with 1.13.2. We should update the internally used version of the SDK and get memchaser 0.5.2 released.
Looks like we can't simply bump the SDK to 1.13.*. After doing that memchaser doesn't initialize anymore because memory.js is not defined. Something is going wrong in there. I might have to take a look at later this week.
Something broke us between 1.11 and 1.12.
Those are the new layout changes which went into 1.12:
So, #163 has the changes required for 1.13.2's... require... statements, and now includes the update to 1.13.2 that actually requires those changes. :)
Travis doesn't seem to be complaining with all of those changes, though I don't know if that means everything's working.
As mentioned on #163 we will do the minimal approach for now and only update the require line for local modules. That will keep backward compatibility with older versions of the SDK.
Release memchaser 0.5.2 with Addon SDK 1.13.2 (#162)