graphql-tag VS node-sql-template-strings

In Apollo Server 3, you could import the gql template literal tag directly from the apollo-server library. This template literal tag is provided by the graphql-tag library and allows parsing a GraphQL query string to an AST that can be used by Apollo and other GraphQL libraries.

Handles parsing, some validation, normalizing and some sort of caching from what I can tell https://github.com/apollographql/graphql-tag/blob/main/src/index.ts

A common use of this feature is compilation of graphql queries, which looks like this.

indentation in Relay.QL Relay and gql, graphql GraphQL template literals

By template strings I mean this (use of Javascript template literals in Apollo). We had a large SpringBoot REST API. Frontend added an Apollo server that simply called our backend and crammed it into a graphql response (ignoring all the work we did for pagination and caching). Later backend inherited this codebase and was forced to maintain it. Both teams spent many man hours on this endeavor with unclear tangible benefits.

This features is so powerful that some awesome libraries were built on it such as Styled Components and graphql-tag.

Ah, I see it. I'm assuming node-sql-template-strings or an equivalent?

There is also some other interesting use cases.

Any reason you chose that over node-sql-template-strings [1], which looks very similar?

[1] https://github.com/felixfbecker/node-sql-template-strings

sql-template-strings is a really simple and elegant solution for parameterized queries.