-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make it work offline #676
Comments
@jedwards1211 There are several solutions for working with GraphQL offline. There's the GraphiQL mac app, there's chromeiQL, there's also altair. |
Looks like these lines are the reason it doesn't work offline out of the box: Lines 30 to 33 in 297edd9
|
@imolorhe Getting rid of these online dependencies, would not only enable GraphiQL to work offline, but also increase privacy and security. |
@caugner yeah, I agree. @asiandrummer, do you remember if there's some historical reason as to why we don't just bundle these? |
@AGS- It would be great to provide bundled build 👍 |
I was thinking for 0.14 of distributing a PS also we may be moving to rollup FWIW. then we can do tree shaking, across the monorepo :) |
Better solution planned here: graphql/graphiql#676
Better solution planned here: graphql/graphiql#676
Would love to see this bundled. Yesterday, it stopped working when my net went off. |
see the webpack or CRA example of how to build your own custom offline bundle! |
@acao It's bundled in Prisma's Nexus so not sure how I can do that? |
@deadcoder0904 then prisma needs to make it available offline! maybe open an issue in their repository? |
our https://github.com/graphql/express-graphql/ bundles graphiql for offline usage, for example |
Better solution planned here: graphql/graphiql#676
Better solution planned here: graphql/graphiql#676
Title says it all. Maybe it's easier to drop GraphiQL into an app when it fetches all of its code and styles from the internet, but remember, some devs occasionally would like to get work done without an internet connection.
The text was updated successfully, but these errors were encountered: