-
Notifications
You must be signed in to change notification settings - Fork 50
AMD Support #5
Comments
I'll look into it. |
I also have this case. I personally use and most projects I've seen use require("knockout") or define(["knockout"], function (ko) { }); |
I think something like this would satisfy 95% of the amd use cases: |
Just uploaded a new version of the plugin https://chrome.google.com/webstore/detail/knockoutjs-context-debugg/oddcpmchholgcjgjdnfjmildmlielhof/details?hl=nl&gl=BE |
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? |
@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. |
it's now working. thanks. this extension is super useful! |
I use knockout in an AMD context with require.js. The extension reports me that "knockout.js is not used in the page (ko is undefined)(...)" (which is true!).
Is there a way to make it works anyway ?
The text was updated successfully, but these errors were encountered: