Description
In the April meeting of the graphql-js-wg, there was discussion about bundling changes in the graphql
package (#4062).
As these changes would also add an exports
field, @benjie suggested that we might want to have a restrictive set of exports
entry points (only graphql
, maybe one or two more?), to discourage from deep-importing from implementation details we do not consider the public interface of the library and which would result in uninteded breaking changes upon e.g. code reorganization.
In this issue, we want to collect libraries and how they are importing from graphql
, to ensure that this is a feasible idea so we can discuss this further in the next graphql-js-wg meeting.
If you are generally opposed to a change like this, this issue (or the next WG meeting) are a good place to write your concerns down :)
Please copy-paste this template into a comment and fill it out:
## `<library_name>`
### Where do you import from in your library?
* `graphql`
### (If you use deep imports) why do you use deep imports?
### Would it be okay for you only import from `graphql`, too?
* [ ] yes
* [ ] no