upgrade to v17

[yaacovCR]

with canary-pr-4288

[vercel]

@yaacovCR is attempting to deploy a commit to the Michael Hayes' projects Team on Vercel.

A member of the Team first needs to authorize it.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 7248227

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[yaacovCR]

proof of concept, see: graphql/graphql-js#4288 (comment)

besides the caveats mentioned there, this version of the upgrade does not preserve backwards compatibility

not sure you will find this helpful, but putting it out there (rather than just deleting after my experimentation) just in case

side-note: this project is amazing!

[hayes]

thanks for sharing this! This will be really useful

I think this will end up needing to be a major release to handle the defaultValue changes properly

[yaacovCR]

I think this will end up needing to be a major release to handle the defaultValue changes properly

This comment inspired graphql/graphql-js#4296 -- not 100% sure, but I wonder if that means that the upgrade to v17 no longer has to be breaking (at least for this library).