Of course not. GraphQL has vastly simplified our backend development, and has also resulted in better coordination between backend and frontend teams. There are so many things which GraphQL gets right - TYPES and schemas, traversing entity relationships, selectively querying fields, builtin API explorer etc. We use REST only for super trivial projects.
(One of the issues the dev team faced was the insane amount of RAM that was consumed by the GraphQL crap in both the FE and BE containers, which was a pain to debug for the FE side because that was an ephemeral container on an EKS environment)
IMHO, GraphQL entices developers on both ends to just be lazy and throw the complexity to the other team, and Ops who has to support both teams and mediate between both sides who just blame the other side for being too dumb.
The key question is do you even need to use a graph database, and for almost everyone not being a social network or other multibillion user count service, the answer is a clear "no, postgres/mysql (depending on familiarity and pain tolerance) is more than enough".
Unfortunately, many developers and even more architects are following "resume driven development" instead of going for something old and tested...
And for the other projects, their paths are littered with the dead bodies of engineers who had been ordered to chase down one of Facebook's hype technologies just because "Facebook does it so we can follow their best example".