Brian M Hunt

The graph looks something like this, from `packages/`: - tko (or knockout) - tko.binding.* - tko.bind - tko.computed - tko.observable - tko.provider.* - tko.provider Various utilities from tko.utils(.*) are imported...

Thanks @Sebazzz ; I've updated visual.zip, hopefully it'll work now.

@caseyWebb This sounds like the right choice, thank you for spearheading this (and thank you @Sebazzz for getting the initial work started on Typescript-ification). What do you propose for next...

@caseyWebb Fantastic. For my next steps, I'll look into typescripting `utils.jsx`, and I'll PR to your branch.

Not really, from my experience. Since observables are anonymous, one just sees the chains of notifications without any indication of origin. Having tinkered, it looks like overloading `computed.fn.updateVersion` with some...

Thanks @bluedev. I believe that mapping functionality will be subsumed by [`ko.proxy`](https://github.com/knockout/tko/blob/master/packages/tko.computed/docs/proxy.md) for tko, but it requires ES6; I haven't yet given much thought to incorporating something like ko.mapping for...

Thanks @abram27 . Incidentally, what're other observable libraries e.g. mobx doing for this sort of issue?

Hi @ricardobrandao – I think Knockout-Validation is a suitable candidate for inclusion in `tko`, and have thought about it. Thanks for noting. @ericmbarnard @crissdev @stevegreatrex Any thoughts, questions, concerns, comments,...

Also noting https://github.com/mattNit/Kavie

I'm moving towards esbuild and nom 7 because esbuild is faster and npm 7 includes workspaces and doesn't require extra utils (i.e. yarn). I'm also removing the Makefile dependencies. There's...