You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For some reason, require("kefir") in can-kefir is getting the Module object in bitcentive. This is now failing because can-kefir tries to set a property on Kefir. But the object is sealed and an error is thrown.
For some reason,
require("kefir")
incan-kefir
is getting theModule
object in bitcentive. This is now failing becausecan-kefir
tries to set a property on Kefir. But the object is sealed and an error is thrown.Kefir seems to be identified as an AMD module:
But what's odd is that kefir does this with the exports object:
I feel like this must be tripping stuff up ...
I can see where
Object.preventExtensions(m);
is called, but not sure why it is.For some reason, while I'm running
can-kefir
's tests. TheObject.preventExtensions()
is called, but called aftercan-kefir.js
has been executed.The text was updated successfully, but these errors were encountered: