Switching to Garnet Causes "ERR unknown command" Redis Error in Node.js Application

[Rainscall]

There is a nodejs application that uses redis without problems, but if I switch to garnet this error will appear:

node:internal/process/promises:288
             triggerUncaughtException(err, true /* fromPromise */);
             ^

[ErrorReply: ERR unknown command]

Node.js v18.19.1

This is the client configuration

const client = redis.createClient({
     url: 'redis://127.0.0.1:3278'
});

This is garnet's log

08::57::25 dbug: GarnetServer[0] [****:3278] Accepted TCP connection from 127.0.0.1:48968
08::57::25 dbug: Session[0] [****:3278] [127.0.0.1:48968] [0014B75E] Starting RespServerSession
08::57::25 dbug: Session[0] [****:3278] [127.0.0.1:48968] [0014B75E] Disposing RespServerSession