Brian Bugh

This functionality would also be really useful for GraphQL. We're trying to replace a custom form setup with VueFormulate and we're running into #161. In our current code, we are...

This is definitely still an issue, I've been fighting with Heroku deployments all day because of it. node v8.9.1 npm 5.6.0 yarn 1.7.0

I wasn't sure if it was worth creating a new issue, we want something like this. We have some internal base images (which themselves used pinned version) that we always...

I removed the package that was complaining, ran `yarn`, and then re-added the package with `yarn add`. This worked for some reason.

FYI, the other(?) official(?) [github cli](https://github.com/cli/cli) can currently do this. It will rename the current `origin` to `upstream` and add your fork as the `origin`. You can do it with...

Edit: see [this comment](https://github.com/gridsome/gridsome/issues/292#issuecomment-475310230) for a better temporary workaround. --- You can work around it with slots. It's a poor solution (considering it's working around a bug of a core...

There is an additional issue that (I think) the first time a graphql image source from `static-query` is compiled, it doesn't work either, but subsequent loads will work. I believe...

Edit: nevermind, there are several issues with this workaround, it seems like webpack will only pick it up if parts of the path are hardcoded ¯\\\_(ツ)_/¯. It isn't usable for...

@Al-Rozhkov, thank you for the reply, I don't have a strong opinion on whether it's a bug or not, it just seems like one to me. I've used a number...

Hi @Al-Rozhkov, one of the reasons we're looking at Gridsome (other than Vue) is `g-image`, because it has built in automatically created responsive images. We have a lot of use...