Change require statements to match the new SDK module layout and update the SDK to 1.13.2 #163

Closed
wants to merge 3 commits into
from

Conversation

Projects
None yet
3 participants
Member

KWierso commented Feb 19, 2013

This should let #162 work.

With this change, I no longer see the error about memory.js.

Member

KWierso commented Feb 19, 2013

Added the commit to update the SDK to 1.13.2 here to see if Travis likes it any better. Seems like it does.

Contributor

whimboo commented Feb 19, 2013

As discussed on IRC the only change necessary for now is the require line for local modules. So I'm going with the minimal change for Memchaser 0.5.2 and keep this pull in the backlog for 0.5.3. Once we are safe in using SDK 1.13 we can do this invasive module update.

Contributor

whimboo commented Feb 19, 2013

I would like to have this in 0.6. @KWierso would you mind updating the pull to the lastest master?

Contributor

whimboo commented Apr 15, 2013

Hi @KWierso. As I have asked 2 months ago, would you be interested to update your pull to the latest master? I would like to see this in our next 0.6 release. Thanks.

whimboo referenced this pull request Apr 15, 2013

Closed

Update Add-on SDK to 1.14 #167

Member

KWierso commented Apr 15, 2013

@whimboo I'll try to get to it sometime this week, but if I don't do it this week, you might be better off just taking it over yourself.

Collaborator

xabolcs commented May 24, 2013

Can I contribute here?

Contributor

whimboo commented May 26, 2013

Absolutely! I would appreciate your help here.

Collaborator

xabolcs commented May 27, 2013

Absolutely! I would appreciate your help here.

Placeholder (only a mirror of this) pull request opened.

Contributor

whimboo commented May 29, 2013

Closing this pull in favor of pull #174.

whimboo closed this May 29, 2013

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment