Is this just a doc change or are future versions of graphql planned which will only support ESM?

@glasser I think with Node 20 and 22 now supporting require(ESM) and almost all bundlers favouring ESM, going ESM-only can't be that far away. I'm not sure if that's planned for v17 or not though, I think it's under discussion. Are you aware of a particular reason to go one way or the other?

@benjie I'm currently working on Apollo Server 5, a release that is focused entirely on updating dependencies (Node, Express, GraphQL-JS). A goal is to have a really simple migration that most people can implement quickly. We are considering making it require GraphQL v17, depending on whether v17 is likely to actually be released soon and how hard the migration will be. If it's not just a matter of updating uses of obscure GraphQL-JS features but actually changing your build system, that's definitely a bit more intimidating for an upgrade, which makes me feel more like we should make AS5 continue to support v16 as well... we'd like there to be no good reason not to do the AS4 to AS5 upgrade as soon as possible.

That said I'm a bit out of date on CJS vs ESM these days and maybe with require(ESM) support most use cases that work with GraphQL-JS v16 will work fine with an ESM-only build out of the box?

require(ESM) is still relatively new, but that they backported it from 22 to 20 (which is in maintenance mode) indicates they have strong confidence in it. I've not yet experimented with it much myself yet; going ESM only 2-3 years ago was something I had to reject due to too many issues, but now I think it's probably worth revisiting.