AMD Support

[timstuyckens]

AMD Support

[timstuyckens]

I'll look into it.
I think it might be possible but their will have to be made conventions about your module name
Like:
require( "knockout")
require("ko")

[luv2code]

I also have this case. I personally use and most projects I've seen use require("knockout") or define(["knockout"], function (ko) { });

[luv2code]

I think something like this would satisfy 95% of the amd use cases:
https://gist.github.com/luv2code/5274902

[timstuyckens]

Just uploaded a new version of the plugin https://chrome.google.com/webstore/detail/knockoutjs-context-debugg/oddcpmchholgcjgjdnfjmildmlielhof/details?hl=nl&gl=BE
Thanks for the feedback!

[Munter]

I was just wondering. Is there a reason why this extension needs to tap into the knockout library supplied by the user instead of packing its own?

[timstuyckens]

@Munter The "core" part of the extension runs in the context of the page of the user. When you run in that context you get acces to the current selected node ($0). In that context, knockout is already present.
Version conflicts are also avoided this way.

[engyii]

it's now working. thanks. this extension is super useful!