I’m not sure how to assist with the error message you posted or able to understand how it’s Apollo related, but from what I understand, a high level / non-Apollo-answer is that “native” ECMAScript module support — generally, not in an Apollo specific way — does not support resolving directories to modules in the same way, but instead requires that the module being imported has a file extension. e.g., rather than
import prop from './directory/, you’d need to do
import prop from './directory/index.mjs'.
As for the other error, do you mind sharing the contents of the error you’re receiving about
(I’ll note you said
-extensions, but you linked to
-extensions, so I assume you’re talking about
From a purely informative perspective,
graphql-extensions is the version of extensibility that we offered in Apollo Server 1.x and 2.x which is being removed in Apollo Server 3.x in favor of the new, more widely adopted, documented and intended for external-use Plugins API. That means it will still be around for a bit longer, but not for long! That said, it could still be in your way, so if you have any error, that would be useful for debugging.