e is locked about daff HOT 4 CLOSED

Thanks! I'm not sure if we should cache the context at all, but may give better performance.
Will look into it shortly.

from daff.

Fixed the issue; case of premature optimization...

from daff.

Definitely works now, but I wonder (like you) if we would want to preserve/cache the context. Haven't done any packages that use V8, so not sure. I wonder if @jeroenooms could help add insight.

from daff.

You can only assign/change objects in the package namespace in the .onLoad function, before the namespace gets locked. But I think what you're doing now (using a separate context for each instance) is usually better, unless you're using some huge js libs which take a long time to load. The new rjade package does both.

from daff.