aurelia-binding is a collection of classes that handle data binding for input, event, checked, select, property observation.
aurelia-templating is a collection of classes that handle html template compilation and rendering, creating
Containers for instances to help proper dependency injections
aurelia-templating-binding is a collection of classes that help you to wire
aurelia-binding together, as by default
aurelia-templating does not understand attributes such as
prop.bind="value". It’s the job of this lib to desugar those binding commands into proper binding expressions and instances. How special bindings, prop of a custom attribute or custom element should be created, is based on the information of resources (
ViewResources class) passed by
aurelia-templating when doing compilation.
aurelia-framework is a collection of classes that wire those thing together, to register resources, default binding language, to translate
aurelia-bootstrapper is a collection of functions that help ensure all requirements of an Aurelia application have been supplied, and init an instance of Aurelia.
From the look of those, it’s not very desirable to use only Aurelia binding. But if insisted, you can use the
Parser to parse expression, and use it to evaluate value from a given object / value.
BindingEngine to observe property of an object, or collection mutations. I bet you will eventually arrive where Aurelia currently is. But maybe you can do it better that what we have, so if you could give some more information on what you are trying to achieve, folks can help better.