Ritchie Martori

@dougwilson What if we adopted [Node's LTS Plan](https://github.com/nodejs/LTS)? It might not be perfect (and IMO it is very complicated), but at least as a user I only would have to...

@dougwilson What if we started with: **Input** A preference file - using a format that supports comments. ``` js var $ = exports // Use Resourceful routing? $.ROUTING_STYLE = 'resource'...

``` js "options": { "validateUpsert": true } ``` Do you have this in your model settings?

Ah... well validation can include validating uniqueness. As far as errors thrown from the database, @raymondfeng do you have any thoughts? Missing an error thrown from the driver sounds like...

> One thought that came to mind looking at this is whether we should move the current ./app yarn workspace to the repository root? And just have one yarn workspace....

``` import * as fop from './../../../fiftyone/app/packages/plugins'; import * as fos from './../../../fiftyone/app/packages/aggregations'; import * as fop from './../../../fiftyone/app/packages/state'; ``` This is not supported. The plugin needs to refer to...

I'm running into the same. Here's a self contained example: https://codesandbox.io/embed/crazy-dirac-04nil?fontsize=14&hidenavigation=1&theme=dark ```jsx import React from 'react' import {Router} from 'react-router' import {Route} from 'react-router-dom' import {createBrowserHistory} from 'history' const myHistory...

> If this isn't possible, what would it take to wrap the primus object in this sort of interface? Below is basically the answer to this part of the issue....

@lpinca this looks promising thank you. Would this make sense as a plugin for primus or am I a rare case (trying to treat `primus` like a `Socket`)?

Well for now, it could be the means of installing for the people who want to use it now. Eventually the packaged app can either make use of this method,...