Remove bundling from yoga?
See original GitHub issueCurrently, yoga supports schema bundling out of the box. This is nice, but it creates a lot of dependencies. And it feels a bit like Express running Webpack for you. It think there is a clear pattern emerging that you use graphql-cli
and its config file to configure and run bundling on your schemas to process imports, and this task should no longer be included in yoga.
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (7 by maintainers)
Top Results From Across the Web
Add yoga bundles and release-tool syncs - OpenDev
Add yoga bundles and release-tool syncs ... run focal-ussuri as smoke tests * remove groovy bundles Change-Id: Ie8a5fe3f3dd10de1b4f180ce05b542896f594393
Read more >Basic Yoga Bundle at EverydayYoga.com
Basic Yoga Bundle Everything you need to deepen in your yoga postures WHAT IT IS YogaOutlet bestseller - A ... Care: Remove stains...
Read more >Yoga Prop Basics Bundle - Charcoal - Halfmoon USA
The Yoga Prop Basics Bundle - Charcoal contains all the professional-grade ... Heatable for the ultimate relaxation (remove cotton cover while heating).
Read more >9 Ground Rules of Product Bundling on Amazon | Zentail Blog
You cannot make them the primary products in your bundle, though they can act as secondary products. You can, for example, bundle a...
Read more >Customer reviews: SANZ Sport Bundle, Remove Odors and ...
Gets out strong odors from workout wear. Gently cleans silk & cloth masks. Easy to use. One person found this helpful. Helpful.
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
This is a broad statement and erroneous assumption of how an individual uses
graphql-yoga
. Schema imports can be applied at any size, not only large schemas.This isn’t true, also. You can use bindings without needing
graphql-cli
.This is a great sentiment to have except that it falls short in the use-case of an opinionated, easy to use/setup solution, i.e.
graphql-yoga
.I believe that @wtgtybhertgeghgtwtg has a good point in that the behavior you are asking to be removed is only dependent on one package, which is dependent on two packages.
This is avoidable by not releasing a new version of graphql-yoga every single time one of it’s dependencies is updated.
tl;dr; - This whole ticket boils down to what we believe is the definition of a good ‘out of the box’ GraphQL server. In the end,
graphql-yoga
is an opinionated, minimal setup GraphQL server – not a GraphQL server with minimal features.graphql-import
has two dependencies,graphql
andlodash
, neither of which are unique.