Consider extracting the config / strategy data into a separate node module?

[jfrux]

For instance, if someone decides to build a node-based express endpoint that wants to detect the page-strategy and not use the view / event binding layers you've built but merely the key binding configs, etc. Something clean that can be used as a central repository for the config data that can be updated separately. Kind of like a swiss-army knife for understanding the requirements of the platform you're running on?

[jfrux]

Or, do you have advice on how I might be able to do this myself. I'm building a react-based app with client and server-side capabilities. Thinking if I had the config data, I could really tap into that quickly and then write my own components / classes to make use of the keybindings and what have you.

[Tanya Byrne]

We have deprecated this project and there are no plans for active development going forward.

Please see the deprecation notice.