apollo-server | production ready JavaScript GraphQL server | GraphQL library

On Apollo server V3 you need to use a different kind of code. It has some breaking changes from V2.

You can do that by following the code below:

As @Jared Smith said, there was a Problem with subscribe() not receiving pubsub, so I kinda hacked something together by going to the server code and changing const pubsub to export const pubsub and I imported it into the resolvers. Seems like an unelegant solution but it does the job for now!

It sounds like you want to create a single executable artifact which requires no server-side configuration or setup to run.

There are a few options for this. You're probably looking for a Javascript bundler, like Rollup, Parcel or Webpack. Webpack is the most widely used, but also generally the most difficult to configure.

Install Parcel with npm i -g parcel, then, add this to your package.json:

As has been commented in the comments section, the issue has been solved by moving the project folder outside the OneDrive directory.

Because it's a synchronized cloud folder, as soon as you install/add/delete/update anything, it's being updated in the OneDrive cloud so the file/folder it's being used in the background and potentially unreachable. If at this time you try to develop the project (gatsby develop or gatsby build) and the file is being used, you won't be able to run it.

I don't think it's a good practice to use a cloud folder because the amount of data synchronized (mainly because of the node_modules) it's something to care about (it's also ignored in the .gitignore for a reason) so moving it to any other folder outside the OneDrive directory should be enough to run your project because the rest of global dependencies, according to your logs, were successfully installed.

app.use(helmet());

is an alias for the following:

Try this:

At the time of release of Apollo Server 3, the protocol used in the graphql-ws library is not yet supported by GraphQL Playground or Apollo Explorer.

see here

It's only advisable to use graphql-ws if interacting with subscriptions via playground is not of much use to you and you're okay interacting with subscriptions solely from your own client that has been setup to use graphql-ws.

To setup your client to use graphql-ws with Apollo. see here.

Checkout the nestjs/graphql documentation page and the other link that you have mentioned. You have to configure your GraphQLModule like this which I don't see in your code.

Nothing heavy, you have to change only few things. As you want to add graphql-subscription then you need to install it also beside subscriptions-transport-ws and @graphql-tools/schema that you already installed. Just install one more that is graphql-subscriptions.