artem avetisyan

Ended up here after a long debugging journey. Same problem as this gem is solving - thanks a lot! - but also it _looks_ like similar problem occurs with `after_save`...

This issue also makes it impossible to use `graphql-playground-react` with [importmap](https://generator.jspm.io/#Y2VjYGBkDM0rySzJSU1hSC9KLMgozNEtyEmsTC/KL81L0S1KTUwucTDUM9czsgAAZHDGnS4A) One way to fix it would be to compile `import imageSource from '../assets/logo.png'` ([here](https://github.com/graphql/graphql-playground/blob/3a09b2e15e12cd1794126e9354e6b2154849f778/packages/graphql-playground-react/src/components/EndpointPopup.tsx#L11)) down to inline data. Currently,...

> Is there a standard way to distribute Docker containers? Images are push into Docker Hub. For example, this is an image built from my repository: https://hub.docker.com/r/artemave/gemstash/ And then docker...

We can put the contents of my repo in a folder in gemstash (let us call it `docker`). Then we can tell travis to build and push to docker hub...

I spiked "docker setup as part of gemstash repository", but abandoned it eventually. In short, travis-ci isn't great for building pipelines.

@smellsblue I addressed your points re configuration and authorization: https://github.com/artemave/gemstash-docker

I agree, building only stable images is the right thing to do. As it stands, my current repo gets the latest gemstash gem from rubygems when it is building. So,...

I am seeing this too. With cheerio. But other modules seem fine. I guess this may have something to do with how cheerio defines methods or something.

This `index.js` - `module.exports = require('./create')()` - creates bm instance at require time. Probably not what I want most of the time. Should it better be `module.exports = require('./create')` ?

Nope. I was adding the latest one. As far as I could see, astroturf expects you to bring your own `css-loader` and does not set any version constraints.