Webpack’ing your GraphQL Documents. This is a short post that describes one of the features we recently built into our Webpack loader for GraphQL documents — graphql-tag — that solves this problem.
When building a GraphQL application, there are benefits that come from placing your GraphQL query documents in their own files rather than inline with your view components. For example, you can get simpler editor and tooling support since the tools can look at static files instead of trying to parse application code. Also, it prevents you from accidentally manipulating queries at runtime. However, until now it has been difficult to do with our GraphQL webpack loader since there was no way to have different queries share GraphQL fragments.
CRUD Tutorial - React, GraphQL, NodeJS, MySQL. Tech Stack: - ReactJS - NodeJS - ExpressJS - GraphQL / Express GraphQL / Apollo Client - TypeScript - MySQL - TypeOrm
How does the Webpacker gem provide "it-just-works" webpack integration with Rails? That simplicity did not come easily. The rich functionality, complexity, and rapid evolution of the webpack ecosystem necessitated extension points beyond a simple Ruby config file.
GraphQL Finland has a different scope, and it's going to be the first Nordic GraphQL focused conference. I'm looking forward to seeing everyone interested in GraphQL at the event.
Today, we launched our event site for GraphQL Summit, the first-ever GraphQL conference. Be sure to check out the full site to see what’s in store.