Consider moving GraphiQL functions to a separate package.
See original GitHub issueWhile useful, they may not be necessary for all users. It is notable that almost all of the package size of graphql-helix
seems to come from dist/render-graphiql.js
. While it would be a breaking change, it is relatively straightforward for users to migrate to something like
import {getGraphQLParameters, processRequest} from 'graphql-helix';
import {renderGraphiQL, shouldRenderGraphiQL} from 'graphql-helix-graphiql';
Issue Analytics
- State:
- Created 3 years ago
- Reactions:10
- Comments:9 (2 by maintainers)
Top Results From Across the Web
Consider moving GraphiQL functions to a separate package. #9
Sounds like a sound idea. We can publish two packages @graphql-helix/core and @graphql-helix/graphiql and just export both from graphql-helix . No breaking ...
Read more >Modularizing your GraphQL schema code
To organize your code, you'll want to split up your schema types and the associated resolvers into multiple files. We get this question ......
Read more >GraphQL Best Practices
Ultimately designing APIs with feature-rich pagination led to a best practice pattern called "Connections". Some client tools for GraphQL, such as Relay, know ......
Read more >GraphQL vs. REST: A GraphQL Tutorial - Toptal
Modern applications generally use several different services, which expose several APIs. We could actually think of GraphQL as a gateway or a wrapper...
Read more >Build and Secure a GraphQL Server with Node.js - Auth0
In this file, the packages to create the server and to use GraphQL are ... Before extending the schema, let's move its definition...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Sounds like a sound idea. We can publish two packages
@graphql-helix/core
and@graphql-helix/graphiql
and just export both fromgraphql-helix
. No breaking changes needed. I’ll circle back to this at my earliest convenience.@talentlessguy Wanna help with this?