Jonathan Haines

Thanks @Exelord I'd be interested in testing it out. I'll see what I can do 👍 The new api looks promising 👀

We've been doing some work to get this branch tested in our apps. We've released a few apps recently and everything is looking good, appears to be working well 👍🏻...

Looks good! You could probably still allow either 👀 ```js import Rollbar from 'rollbar'; export let rollbar = null; export function installRollbar(rollbarOrConfig) { if (rollbarOrConfig instanceof Rollbar) { rollbar =...

> Then we still would have to maintain rollbar version as it will be a direct dependency It could be a peer dependency, whose version could be fairly loose. It...

I've removed the code changes that were in this PR

If it helps, I use [px-to-rem](https://github.com/cuth/postcss-pxtorem). I prefer the idea of keeping plugins/modules to a small maintainable set of features

My current day job is working with one team on a larger angular app written by multiple teams. We test with karma and jasmine. Our component classes (controllers and services)...

You can use something like [`resolve-pkg`](https://github.com/sindresorhus/resolve-pkg) to resolve paths relative to a package directory ```js const resolvePkg = require('resolve-pkg') ... includePaths: [ resolvePkg('bootstrap-sass/assets/stylesheets'), ], ```

Looking at the `mirageGraphQLFieldResolver`, it may need additional checks for lists that are a `GraphQLInterfaceType` or `GraphQLUnionType`? https://github.com/miragejs/graphql/blob/8364bb66dae872ba7c208fe199acebf8855adb71/lib/resolvers/mirage.js#L29-L41

Ok, thanks! I hadn't considered adding a field resolver