Jon
Not sure if we want this issue here or in [nanomorph](https://github.com/choojs/nanomorph), but looks like proxy nodes are leaked when a component is morphed to a new location in the dom....
I wanted to open a thread about what utils might make sense to add to core. One that I am always recreating is `letter-spacing`: ```js { prop: 'letter-spacing', vals: {...
An idea been toying with is per-breakpoint values. This could be handy when doing something like font sizes for a site. Not sure if this would be a convoluted addition...
Right now regex is verbose, was working on this too late at night. Something more along the lines of (currently not working): ```js /class=(?:"([^]+?)"|'([^]+?)'|\$\{([^]+?)\})/ig ``` to match tagged template stuff...
Allow a second argument into `page` to define a dynamic/fallback content entry. Example in context of `choo`: ```js var page = require('nanopage') var p = page(state.href, { source: `/bundles/${state.params.id}.json`, loaded:...
Potentially allow lookups for keys not formatted like a path. This is mainly for allowing edge-case arbitrary content (I've been doing this), for example your content object could be shaped...
Wrapper?
Curious if we need the wrapper function, instead of just directly exporting the class. Doing this would allow for easy extending: ```js var Nanopage = require('nanopage') class Page extends Nanopage...
We should get all the tests matching most up to date choo. Right now the examples still run fine, just want to make sure we've got up to date deps...