Hi @mickhansen,
thanks for this library which is extremely useful.
I wanted to check if you have looked at GraphQL-Js v17.
The alpha has been released about 2 months ago, the release notes are here
There are a number of reasons why people might need to start using v17, even if it's just in alpha stage.
I was wondering if you would consider releasing a version of graphql-sequelize that is compatible with GraphQL-Js v17.
From an high-level look, it looks like the main issue is around the ESM only strategy adopted by graphql-js.
Nor sure if you are using any of the removed functions, hopefully not since they were marked as deprecated already.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Hi @mickhansen, thanks for this library which is extremely useful.
I wanted to check if you have looked at GraphQL-Js v17. The alpha has been released about 2 months ago, the release notes are here
There are a number of reasons why people might need to start using v17, even if it's just in alpha stage. I was wondering if you would consider releasing a version of
graphql-sequelize
that is compatible with GraphQL-Js v17.From an high-level look, it looks like the main issue is around the ESM only strategy adopted by
graphql-js
. Nor sure if you are using any of the removed functions, hopefully not since they were marked as deprecated already.Thanks for your time.