Change dependency tree structure

[schickling]

The current dependency tree looks similar to this:

     +-------------+
     |             |
     | graphql-cli |
     |             |
     +------+------+
            ^
            |
 +----------+----------+
 |                     |
 | graphql-cli-prepare |
 |                     |
 +----------+----------+
            ^
            |
+-----------+------------+
|                        |
| graphql-binding-static |
|                        |
+------------------------+

This means for every change that's introduced in graphql-binding-static a new version of graphql-cli-prepare and graphql-cli needs to be released and installed in order to use the latest graphql-binding-static changes.

I'd like to change the dependency hierarchy in a way to "colocate" dynamic and static bindings (e.g. put prisma-binding next to the static binding generator for prisma).

Thoughts and idea on this are highly appreciated. 🎉

[danielkcz]

Just my two cents, but perhaps it could be a good candidate for a monorepo structure (eg. with lerna) and basically auto-deploy all packages when something changes so all of them have the same version and it's easy to track the compatibility. For example the Storybook is setup like that with its numerous addons (see npm).

[kbrandwijk]

I'm not particularly a fan of monorepos, unless it's really, really tightly coupled (like multiple components of the same app), like in graphql-playground.