You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be nice to understand how to support a context where use of the fs module is injected, i.e. in a webpack loader. I would like to be able to use this library in graphql-loader, but as-is this library accesses the fs module directly.
The text was updated successfully, but these errors were encountered:
Hi there, it's The Guild :) We're working on a new version of GraphQL Config. The goal is to make it platform agnostic, flexible enough to use with any tool and framework, reduce the bundle size and a lot more and what's even more important, bring it back to life and keep maintaining.
New changes #162 are already merged into master and v3.0.0-alpha.13 is released.
With new GraphQL Config we decided to make extensions a first class citizen and let them actually extend GraphQL Config's logic.
Right now extensions can enable Config to load a Schema from different sources, an example can be found here. Because we moved the schema loading logic outside GraphQL Config, we named it Loaders, it was possible to introduce a loader for files on GitHub or a loader to extract schema from typescript and javascript files. I think it opens up the Config for variety of use cases.
Do you think it covers your story? We'd be happy to collaborate on this one and hear your suggestions!
It would be nice to understand how to support a context where use of the fs module is injected, i.e. in a webpack loader. I would like to be able to use this library in
graphql-loader
, but as-is this library accesses the fs module directly.The text was updated successfully, but these errors were encountered: