Shows the knockout context & data for the selected dom node in a sidebar of the elements pane.
Knockoutjs debugging extension. Adds a extra sidebar in the elements pane of the chrome dev tools with the relevant knockout context and data for the selected element. Very usefull if you got large/nested viewmodels. Allows to add tracing to every observable/computed. Allows to edit observables from the console.(https://github.com/timstuyckens/chromeextensions-knockoutjs/wiki/Editing-viewmodel-binding-values) Source code is on github: https://github.com/timstuyckens/chromeextensions-knockoutjs MIT license. Tip (based on comments) You can view the content of any observable in the viewmodel in the '$root_toJS' variable.
- (2020-01-28) Vivek Pandey: Fantastic
- (2020-01-15) Stephane Berube: broken in 2020
- (2019-03-01) Ron McCranie: Doesn't work. Either that, or it's extremely confusing to get it to work. Looking for something easy.
- (2019-01-23) Mohammed Farhadur Rahman: I've been using this extension for a couple years now. I think it's essential for Magento front end development where KO is used.
- (2018-11-26) Attila Tóth: I used to rely on it, but it's not working for me with 3.5.0 RC2.
- (2018-06-14) Daniel Clarke: Good for checking on knockout contexts in dev tools, but my god, it becomes slow as treacle even on the smallest of views, will remove from chrome now. would recommend if in a real bind, would not recommend for day to day use.
- (2018-05-14) Ben Ashley: Does what it says but limited filtering options for suggestions vs issues.
- (2018-04-20) Phillippa Hutton: cant live without this
- (2018-03-16) Krunal Parmar: Not able to see values in Knockout Context panel. Can only see observables only No way to dig into obesrvable.
- (2018-02-09) MrOnosa: I'm going to parrot what Andy Hawkins said two years ago: !!! If you experience slowness when debugging in the elements tab !!! Go to extensions and then options and turn off the first checkbox for serialization. This will fix the issue.
- (2018-02-08) Steve Ottenad: Its a valuable tool, but only because there are none else like it. There is a memory leak or something that routinely crashes my tab.
- (2018-01-25) Andrew Hood: Invaluable tool for doing coding with KOjs. Thanks a bundle.
- (2017-09-14) Paul Hoke: Great tool. I don't know how I could do my job without it.
- (2017-08-17) David R. Noel: Necessary for development in any Knockout environment.
- (2017-08-17) MobiusHorizons: Apparently this no longer functions in recent versions of chrome. I was unable to get it to show up.
- (2017-07-10) Chris Hawkes: doesn't work
- (2017-07-10) Debdeep Majumder: awesome
- (2017-06-10) Yaniv Abo: Grate Tool
- (2017-05-24) Michael Broussard: Works great
- (2017-04-26) Albert Puig: Está muy bien para proyectos simples. Con iframes no funciona.
- (2017-04-01) Jean-Sebastien Binette: So far so good. THANK YOU!!
- (2017-01-17) Michael Pavlak: Must have tool when developing a Knockout application. I have worked on several applications of decent size and never ran into any performance issues noted by others. I imagine that if you have performance issues, your models are probably insane. :)
- (2017-01-12) Dave Lee: Very good,thanks
- (2017-01-10) Dirk Reuschling: It's good to see whats in the model, but it breaks the Chrome process with a "Ah Snap" message when I check the properties of a specific html element.
- (2017-01-04) Karmjit Singh: Awesome, must have for each knockout developer
- (2020-01-22, v:2.6.3) Tevis Woods: Port for new Microsoft Edge
I was hoping you could port this awesome tool to the new Microsoft Edge browser, which runs on the same engine as chrome. They offer a porting solution here: https://docs.microsoft.com/en-us/microsoft-edge/extensions/guides/porting-chrome-extensions Thank you!
- (2019-12-17, v:2.6.3) Cristian Ferrero: Problem with the order of the attributes
Hi. I use the plugin daily, from today I noticed that the attributes are disordered (previously shown in alphabetical order). This makes it very difficult to find attributes in very large contexts. Is there any way to solve it? Thanks for all. Regards.
- (2018-11-10, v:2.6.3) Why this very cool and useful extension is not getting updates?
Consider updating this extension please, it's great but many developers are facing some issues mostly with new knockout js versions and browser updates as well.
- (2018-02-05, v:2.6.3) Adrian Barglazan: sometimes chrome crashes
Hello, It happened multiple times that chrome crashed - actually freezed - when I click on inspect some pages which contain knockout. It is not something that I can reproduce - happens from time to time
- (2018-01-11, v:2.6.3) Rodica Cladicov-Walker: knockout.js is not used in the page (ko is undefined).
I am getting this error in the ko tab: knockout.js is not used in the page (ko is undefined). Why?
- (2017-11-13, v:2.6.3) Kirill Penkin: reference a ko context from global scope
it's a great thing you can see a ko context attachet to an element. It'd even better to be able to reference it from console. We use ko with durandal.js, so all our view models are hidden in their scopes and as a result i need my debug be attached to a vm's life cycle. If I could choose an element and then reference it's vm (the variable I see in knockout context window) it'd help me a lot. Is this feature available somehow?
- (2017-09-08, v:2.6.3) Santhosh G: Disabled KnockoutJs context debugger icon
Added Knockoutjs context debugger but it is disabled. Tried all ways, but there is no use. Help me on this.
- (2017-04-05, v:2.6.3) John Pavek: Add Tracing to extension button menu
Would it be possible to have the extension button menu also contain the Enable tracing command? It would be a nice quality of life perk. Thanks!
- (2017-01-29, v:2.6.3) Omar AlJaber: obsrevable
the observable coming as function, is there any way to display the values of the observable
- (2017-01-06, v:2.6.3) Barry Owens: Webpack error fixed
When using webpack and error is shown: "knockout.js is not used in the page (ko is undefined)" A fix for this is to expose knockout globally using: var ko = require('knockout'); window.ko = ko; Might be worth including in the overview or else implementing a fix to avoid the error
- (2016-03-31, v:2.6.3) Squiggley Woo: Webpack
- (2016-03-08, v:2.6.3) jenish rabadiya: Why does this app needs the permission for "Read and change all your data on the websites you visit"
It has no doubt that this is the great extension for developer but i am very enthusiastic to know what is the reason app is asking for this permission and how app utilize this permission to provide great debugging experience to the developer.