Ryan Glover

I think there may be a way to do this where we offer a stripped down, OS browser container type of thing and wire up a cache like TuskDB (or...

I think joystick.js/db will be the best way to do this. Maybe even make it so you can "switch" databases dynamically based on the page/view. Would also be good to...

Still interested in this idea but closing for now.

You can temporarily circumvent this by using inline styles: ```javascript render: ({ props }) => { return ` ${props.callout} `; }, ```

Don't forget to mention how to handle errors for various API calls (e.g., uploaders): ```javascript test.that('uploader throws error for incorrect file type', async (assert = {}) => { const response...

Mock that just came to mind... ```javascript import SomeComponent from '/ui/blah'; joystick.spa.router({ '/path/to/:thing': (req = {}, res = {}) => { // req?.params req?.query req?.url // res.render() is only res...

Thinking about this again and routing via links. Could do something like `joystick.spa.location('/path/to/go/to')` which only maps to routes defined via the routes table above. Another option (though could confuse) is...

I keep coming back to this and the solution seems to be doing a client-side router with dynamic fetches of pages. I just realized this isn't too far from how...

Another riff on this. You could also do an additional folder at `/ui/spas` and just have Joystick components that represent an SPA (designated by a `routes` option on the component)....

Was thinking about this the other night and there's potential to automate it. Basically, the same way that we handle a mount for layouts (dynamic import) could hypothetically be used...