graphql-middleware | Split up your GraphQL resolvers in middleware functions | GraphQL library

The error message points to a failed preflight request, which is an OPTIONS request without credentials. Such preflight requests should be handled by the app.use(cors(corsOptions)) middleware. But this middleware comes rather late, so this will not work if any of the earlier middlewares (e.g., app.use(passport.session())) already responds to this OPTIONS request.

The screenshot of the OPTIONS request with Content-Length: 8 in the response seems to imply that this happens here.

It's strange but the problem was with this import { GraphQLDateTime } from 'graphql-iso-date'; package.

After removing it from the schema, it started working.

Finally figured out a solution after visiting the NPM page for axe-cypress.

The problem here is certainly with NPM and the packages you are trying to install rather than anything to do with Docker.

Unfortunately, I am not able to reproduce the exact error that you are facing. That could be because:

• something changed in the time between now and whenever this problem occurred;
• there are some essential details that you are not showing us.

Either way, there's a general way in which such issues are solved, which should help. But first an explanation.

NPM's package (dependency) management mechanism allows packages (dependencies) to have:

• (direct) dependencies - installed automatically with the package;
• peer dependencies - have to be manually installed by the consumer of the package.

However, NPM does not allow multiple versions of the same package to coexist.

Also, as you may know, packages use standard semantic versioning, which means that a major version change indicates a breaking change.

Due to these two reasons, clashes occur if one package requires dependency A to be v1, while another wants the same dependency A to be v2.

NPM v7 was recently released and this is the version that current (as of November 2020) node:current images use.

Probably the biggest changes brought about by NPM7 relate to peer dependencies - NPM should now be able to install them automatically, if possible. Read more here.

As described in the document, in cases where it's not possible to solve the conflicts, NPM should now throw errors rather than warnings, which is what you are seeing.

I, on the other hand, only managed to get warnings and no errors using your setup and NPM v7.0.8, and I don't know why. The problems reported were essentially the same, however, so the resolution ought to be very similar.

The only solution that I'm aware of is manual conflict resolution - the developer needs to adjust their dependencies to play along.

In your specific case the problem seems to be with the graphql package. The latest graphql package is v15, which is also a peer dependency of the latest type-graphql package (v1).

However, apollo-server-express has a few dependencies, which apparently only support graphql up to and including v14.

While you wait for apollo-server-express to fully support v15, you may opt for graphql v14 altogether by downgrading the only package that requires v15. So if you change your npm install to this:

How about:

I used to get this error due to low or intermittent internet bandwidth.