Error in while starting node server - Baseclass undefined

[kumark86]

We are trying to incorporate the redis cache in node server. But throwing below error

node_modules/@redis/client/dist/lib/commander.js:5

function attachCommands({ BaseClass, commands, executor }) {
                          ^
TypeError: Cannot destructure property 'BaseClass' of 'undefined' as it is undefined.

Node version: 14.15.0
Redis Version: 4.5.1

Please help me to resolve the issue.

[leibale]

Can you please share the code that calls createClient? Are you calling attachCommands directly (just making sure..)?

[kumark86]

Code used to create client added below

const redis = require('redis');

const cacheClient = redis.createClient({
  // rediss for TLS
  url: `rediss://${cacheHostName}:6380`,
  password: cachePassword
});

Also I didn't call the attachCommands directly.

[leibale]

@kumark86 I'm actually not sure what is going on.. I tried reproducing it locally but I didn't manage to get this error..
Can you please share the result of npm ls @redis/client (run it in the project root directory)

[kumark86]

@leibale This issue occur only in production after deployment. We using kubernetes for deployment and very strange thing is like some of the docker are no issues and running perfectly. But of the docker(node server) not up and shows the above error.

Result of npm ls @redis/client
npm WARN npm npm does not support Node.js v14.15.0
npm WARN npm You should probably upgrade to a newer version of node as we
npm WARN npm can't make any promises that npm will work with this version.
npm WARN npm Supported releases of Node.js are the latest release of 6, 8, 9, 10, 11, 12.
npm WARN npm You can find the latest version at https://nodejs.org/

`-- (empty)

[leibale]

Seems like @redis/client (which is a dependency of redis) is not installed, and maybe some other packages are missing as well. I'm not too sure what went wrong there, but this might help:

1. Remove the current package-lock.json and node_modules
2. Run npm install
3. Copy the new package-lock.json to the docker (probably using git commit + push, depending on your envirement..)
4. Run npm ci in the docker
5. It should work

[zdegner]

@kumark86 Did you ever find out what the issue was here? We suddenly started seeing this issue with some of our containers after an AKS (Azure Kubernetes Service) update. Kubernetes went from version 1.25 to 1.26. We have a service mesh and security in play (Linkerd, Aquasec) so we aren't quite sure yet if that is somehow related.

Update: for us the error above was caused when Dynatrace was enabled in the Kubernetes cluster.