close
UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer, Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer, UnhandledPromiseRejectionWarning, Error: You must await server.start(), server.applyMiddleware() at ApolloServer,

[Solved] UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer

by

Hello Guys, How are you all? Hope You all Are Fine. I am trying to start my nextJs server and I am facing the following error UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer In NestJs. So Here I am Explain to you all the possible solutions here.

Without wasting your time, Let’s start This Article to Solve This Error.

Contents
  1. How UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error Occurs ?
  2. How To Solve UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error ?
  3. Solution 1
  4. Solution 2
  5. Summery

How UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error Occurs ?

I am trying to start my nextJs server and I am facing the following error:

UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer

How To Solve UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error ?

  1. How To Solve UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error ?

    To Solve UnhandledPromiseRejectionWarning: Error: You must await server.start() before calling server.applyMiddleware() at ApolloServer Error just downgrade to apollo-server-express@^2 and your error will be fixed.

Solution 1

This is a known bug with an open issue So that For now, you can downgrade to apollo-server-express@^2

Solution 2

Using “apollo-server-express”: “^3.0.0”, there’s already a fix.

Summery

It’s all About this issue. Hope all solution helped you a lot. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?

Also Read

Leave a Comment