Knut Melvær

To clarify: It's not intentional, we just haven't gotten around to fixing this yet. I've put it on the backlog of things to do. No ETA at the moment I'm...

Thanks for reporting – we'll look into it!

Haha – this is gold @hcavalieri. It would have been cool if we could've made this a bit easier for you, but cool that we know have a way to...

[Here's the documentation](https://www.gatsbyjs.org/docs/graphql-reference/#group), and [some more documentation](https://github.com/gatsbyjs/gatsby/blob/d5b137edff6c991ab6523616ba535f257f622f74/docs/docs/schema-connections.md#groupconnection) for Gatsby, and [here's an example](https://www.gatsbyjs.org/docs/adding-tags-and-categories-to-blog-posts/#make-a-tags-index-page-tags-that-renders-a-list-of-all-tags).

Yes, that's my understanding too.

I think this will be solved with the next release.

Thanks for reporting @david-j-davis! I have just tried to reproduce the issue (pretty much on exactly the same environment), but I don't get the same issue. Now that the deployment...

Thanks for reporting – we will look into it when we get the chance!

Yes! We're actually starting that work now, and I believe we're going right to 5.

It runs fine as a npm script 👍 I suspect that it's the node-sass dependency that is the culprit: ```sh npm ls node-gyp [email protected] ~/Desktop └─┬ [email protected] └─┬ [email protected] └─┬...