Hans-Jørgen Vedvik

The current master branch should be compatible with 0.7 already. Here is the [gridsome.config.js](https://github.com/gridsome/gridsome-starter-wordpress/blob/master/gridsome.config.js) file with the templates config. And [here](https://gridsome-starter-wordpress.netlify.com/) is the starter running v0.7.3 on Netlify :)

@helloiamlukas Yes, I agree. We should let `g-image` lazy load external images since Gridsome already has the ability to do it built-in. Right now it's only possible by passing a...

Awesome, @tennox! I'll take a look at the PR pretty soon :) Preprocessing with dynamic `src` with `g-image` is possible, but with some limitations. The value of the `src` attribute...

Can you check if this filter would work better for you? ```gqp filter: { collections: { id: { eq: "fC2enKhGoDy6FwhgsPjK7e" } } } ```

@souljorje @Timmitry Using `String` as default type will probably work in many cases. But if the field usually is, for example, a date with arguments or an object with subfields,...

I'm not sure if setting a custom `NODE_ENV` value is a good idea. Gridsome and plugins often check it for either `development` or `production` to disable/enable behaviors. It might be...

The problem with dynamic `src` is that webpack doesn't have access to the JavaScript variables. We can look into [`require.context`](https://webpack.js.org/guides/dependency-management/#requirecontext) and see if that will make dynamic `src` paths possible.

`require("!!assets-loader?${query}!${value}")` generates a string based on a static `src` value. webpack *can* handle dynamic requires, but because it doesn't see the dynamic value at compile time, it generates a list...

@CraigHead I'm not able to reproduce this. But I'm working on a Mac, so it can be a problem on Windows. I will do some tests one of the next...

@CraigHead Sorry for the delay on this, I've installed Windows 10 on my Mac now and started a new `gridsome-starter-blog` project. But it seems to work as expected for me....