Fixing NestJS Error in Production: Cannot Find Module ‘@nestjs/microservices’

Updated: December 31, 2023 By: Guest Contributor Post a comment

Understanding the Error

When developing applications with Node.js and NestJS, encountering the Cannot Find Module ‘@nestjs/microservices’ error typically indicates that your application is attempting to import a dependency that isn’t currently installed in your production environment. Although this works fine in your local development due to presence of all necessary packages, the production environment relies only on packages declared as dependencies in your package.json file.

Several reasons can cause this error, such as simply forgetting to install the required modules, issues with the package management setup, or a mishap during the build or deployment process. The @nestjs/microservices package is particularly used for building microservice features with NestJS, and if your app uses such features but fails to load the required module, the error will occur.

Verifying Package Installation

To address the problem, first ensure that the @nestjs/microservices module is properly listed in the dependencies within your package.json. Besides checking manually, you can use the Node Package Manager (npm) or Yarn to install the package. Running npm install @nestjs/microservices or yarn add @nestjs/microservices in your project directory will add the module to the list of dependencies and install it.

After updating your dependencies, you must build your application again. Utilize your build script, typically something like npm run build, to compile your TypeScript code into JavaScript. The resultant output is what should be deployed to your production environment.

Checking Your Build Pipeline

Sometimes the problem isn’t with the installation but with the deployment process. Make sure that the pipeline properly installs all the dependencies before rolling out the application to production. This involves configuring your Continuous Integration/Continuous Deployment (CI/CD) setup to run an installation command as part of your deployment process. Additionally, make sure your environment is set to production by setting the NODE_ENV environment variable to production. In production, npm will not install modules listed under devDependencies, so the @nestjs/microservices package must be under the dependencies section.

Checking Environment Consistency

It’s possible that the environments for development and production differ significantly, leading to inconsistencies that cause this error. To mitigate this issue, make use of Docker or another containerization tool to standardize your environments. With Docker, you can build an image of your application that includes all the necessary dependencies, and use this same image for both development and production, ensuring they are identical.

Working Code Example

Here’s a small example illustrating how to include the necessary microservices module and run a simple NestJS application:

import { NestFactory } from '@nestjs/core';
import { AppModule } from './app.module';
import { Transport } from '@nestjs/microservices';

async function bootstrap() {
    const app = await NestFactory.create(AppModule);
        transport: Transport.TCP

    await app.startAllMicroservicesAsync();
    await app.listen(3000);



  • The NestFactory.create() method initializes the application based on AppModule.
  • The app.connectMicroservice() method sets up a microservice with TCP transport.
  • app.startAllMicroservicesAsync() starts the microservice.
  • Finally, app.listen(3000) tells the main application to listen on port 3000.

Before running this code, make sure to install the @nestjs/microservices package, and include it in your package.json. Additionally, ensure you have a corresponding AppModule configured for your microservices.

In this guide, we have explored common causes behind the Cannot Find Module ‘@nestjs/microservices’ error in production environments and provided steps and considerations to address the issue, keeping in mind to always verify package installations, build pipelines, and environment consistency to prevent such errors from occurring in the future.