Error while running nestjs in production mode, cannot find module

Question

I have implemented a generic class as below which might be causing the problem,

    import { Logger } from '@nestjs/common';
    import { PaginationOptionsInterface, Pagination } from './paginate';
    import { Repository } from 'typeorm';

    export class EntityService<T> {
      private repository: Repository<T>;
      constructor(repository) {
        this.repository = repository;
      }

      async getEntityWithPagination(
        options: PaginationOptionsInterface,
      ): Promise<Pagination<T>> {
        const [results, total] = await this.repository.findAndCount({
          take: options.limit,
          skip: (options.page - 1) * options.limit,
        });
        return new Pagination<T>({ results, total });
      }
    }

and using with other entity services, such as

    @Injectable()
    export class CarService extends EntityService<CarEntity> {
      constructor(
        @InjectRepository(CarEntity)
        private carRepository: Repository<CarEntity>,
      ) {
        super(carRepository);
      }

the code is working perfectly fine with npm run start:dev but throwing below error when trying to run with production npm run start:prod

        internal/modules/cjs/loader.js:582
            throw err;
            ^

        Error: Cannot find module 'src/shared/entity.service'
            at Function.Module._resolveFilename (internal/modules/cjs/loader.js:580:15)
            at Function.Module._load (internal/modules/cjs/loader.js:506:25)
            at Module.require (internal/modules/cjs/loader.js:636:17)
            at require (internal/modules/cjs/helpers.js:20:18)
            at Object.<anonymous> (/home/tejas/Code/web/project/dist/car/car.service.js:27:26)
            at Module._compile (internal/modules/cjs/loader.js:688:30)
            at Object.Module._extensions..js (internal/modules/cjs/loader.js:699:10)
            at Module.load (internal/modules/cjs/loader.js:598:32)
            at tryModuleLoad (internal/modules/cjs/loader.js:537:12)
            at Function.Module._load (internal/modules/cjs/loader.js:529:3)
        npm ERR! code ELIFECYCLE
        npm ERR! errno 1
        npm ERR! [email protected] start:prod: `node dist/main.js`
        npm ERR! Exit status 1

I have tried deleting dist folder, but still no luck. I have tried updating packages also, package.json is as follows. I have no clue how to debug this.

        dependencies": {
            "@nestjs/common": "^5.5.0",
            "@nestjs/core": "^5.5.0",
            "@nestjs/jwt": "^0.2.1",
            "@nestjs/passport": "^5.1.0",
            "@nestjs/typeorm": "^5.2.2",
            "bcryptjs": "^2.4.3",
            "glob": "^7.1.3",
            "passport": "^0.4.0",
            "passport-http-bearer": "^1.0.1",
            "passport-jwt": "^4.0.0",
            "pg": "^7.7.1",
            "reflect-metadata": "^0.1.12",
            "rimraf": "^2.6.2",
            "rxjs": "^6.2.2",
            "typeorm": "^0.2.9",
            "typescript": "^3.2.2"
        },
        "devDependencies": {
            "@nestjs/testing": "^5.5.0",
            "@types/express": "^4.16.0",
            "@types/jest": "^23.3.1",
            "@types/node": "^10.12.18",
            "@types/supertest": "^2.0.7",
            "jest": "^23.5.0",
            "nodemon": "^1.18.9",
            "prettier": "^1.14.2",
            "supertest": "^3.1.0",
            "ts-jest": "^23.1.3",
            "ts-loader": "^4.4.2",
            "ts-node": "^7.0.1",
            "tsconfig-paths": "^3.5.0",
            "tslint": "5.11.0",
            "webpack": "^4.28.2",
            "webpack-cli": "^3.1.2",
            "webpack-node-externals": "^1.7.2"
        },

Tejas · Accepted Answer · 2019-01-05 05:22:48Z

120

I have found the issue, it was because of absolute path while importing the class.

import { EntityService } from '../shared/service-common'; //correct way

import { EntityService } from 'src/shared/service-common'; // wrong autoimport

To fix auto import, I have added this setting in VS Code

"typescript.preferences.importModuleSpecifier": "relative"

answered Jan 5, 2019 at 5:22

Tejas

2,4753 gold badges20 silver badges27 bronze badges

Sign up to request clarification or add additional context in comments.

4 Comments

kaijun Over a year ago

hello, I want to know why I add ` "paths": { "src/*": ["src/*"] } ` in tsconfig.json also throw error when use absolute import.

Rafi Henig Over a year ago

Would you please explain why is that so? Thank you very much!

Jacky Over a year ago

is there any way that we can use this "src/.." path when importing?

Masih Jahangiri Over a year ago

It's not a good solution, because I want to use absolute path.

H Aßdøµ · Accepted Answer · 2021-12-17 21:49:10Z

69

Delete the dist directory and run again with: npm run start:dev

edited Dec 17, 2021 at 21:49

H Aßdøµ

3,0555 gold badges30 silver badges37 bronze badges

answered Jul 7, 2020 at 20:42

Manuel Montero

7255 silver badges2 bronze badges

6 Comments

Marcin Pevik Over a year ago

Lots of thanks. Nest is Angular-like, but has some weird problems Angular doesn't have.

Felix Dolderer Over a year ago

This doesn't answer the question, as it runs the app in development mode, not in production mode.

Aissam Jadli Over a year ago

this fixed it for me, dunno why though

OhadBasan Over a year ago

that fixed it for me. but why?

Ahmed Adewale Over a year ago

This fix it for me. Many Thanks, would've spent eternity fixing what is not broken many thanks

|

RicardoVallejo · Accepted Answer · 2023-03-12 08:08:20Z

7

Just ensure that your script is pointing to main.js inside dist folder.

"start:prod": "node dist/src/main"

answered Mar 12, 2023 at 8:08

RicardoVallejo

1,13610 silver badges13 bronze badges

Comments

Andrew Forman · Accepted Answer · 2019-11-19 22:36:09Z

5

I've also seen the same problem due to a capitalized reference, when the filename is lowercase:

import { SomeClass } from './Some.class';

but the file was named some.class.ts

Fixing the import resolved the error.

answered Nov 19, 2019 at 22:36

Andrew Forman

912 silver badges5 bronze badges

2 Comments

1252748 Over a year ago

My eyes have glossed over from staring at this too long and I never would have caught this without your suggestion—Thank you!

Ravi Bhanushali Over a year ago

Such a silly thing, but big help! not sure why it even allows this when i use wrong case on local

MobinS · Accepted Answer · 2022-08-06 12:29:18Z

5

I think it's worth mentioning that having js/ts files(that import modules) outside the src folder might cause issues when running start:prod

I had a seed.ts for seeding to my database with Prisma ORM, I moved it inside the src folder and resolved the issue.

edited Aug 6, 2022 at 12:29

answered Jul 30, 2022 at 8:55

MobinS

612 silver badges4 bronze badges

2 Comments

Goutham J.M Over a year ago

Your answer could be improved with additional supporting information. Please edit to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers in the help center.

Chidiebere Nwachukwu Over a year ago

This was my exact problem, and this is valid because files outside of the src folder aren't accounted for by your tsconfig, so moving the seed file from the prisma folder generated by prisma init into my src folder solved the error.

Abdiel Cruz Robaina · Accepted Answer · 2022-07-24 23:29:46Z

4

Sometimes the error can be caused by existing code outside the SRC folder (eg Typeform migrations, etc) which causes the compilation inside DIST to enter one level of folders (eg dist/migrations, dist/src) which makes the main file not be in the correct location.

answered Jul 24, 2022 at 23:29

Abdiel Cruz Robaina

412 bronze badges

Comments

Masih Jahangiri · Accepted Answer · 2022-01-23 19:02:29Z

3

A solution

Remove the noEmit from compilerOptions of tsconfig.json file.

answered Jan 23, 2022 at 19:02

Masih Jahangiri

11.1k4 gold badges54 silver badges59 bronze badges

1 Comment

Shadoath Over a year ago

Why would this help?

achyuth Reddy · Accepted Answer · 2022-07-01 08:27:51Z

2

I got this resolved by deleting the generated files and recreating it eg: dist folder

answered Jul 1, 2022 at 8:27

achyuth Reddy

291 bronze badge

1 Comment

Liam Over a year ago

Yes, this has already been said

Mohamed Kamal · Accepted Answer · 2022-12-22 18:25:26Z

2

If your problem doesn't include relative directory problem then try to remove the dist folder then try to npm run start:prod again, if you have a tsconfig.build.tsbuildinfo file delete it as well.

edited Dec 22, 2022 at 18:25

answered Dec 17, 2022 at 19:42

Mohamed Kamal

233 bronze badges

Comments

Alwin · Accepted Answer · 2022-02-08 17:09:13Z

0

I forgot to install these two packages that were required by mikro-orm. Installing solved my issue:

yarn add @mikro-orm/core @mikro-orm/nestjs

edited Feb 8, 2022 at 17:09

answered Feb 8, 2022 at 16:59

Alwin

1,10715 silver badges25 bronze badges

Comments

Jorge Guerra Pires · Accepted Answer · 2023-10-23 17:50:59Z

0

In my case the solution was "stupid": you need to give a name for the folder without space. If you write: codes projects, it cannot find, you have to write codes_projects. I am adding this solution since it is too trivial, and likely the last place people will look.

answered Oct 23, 2023 at 17:50

Jorge Guerra Pires

63211 silver badges25 bronze badges

Comments

RicardoVallejo · Accepted Answer · 2024-03-23 13:45:08Z

0

May not be relevant for many people but in my case it was all caused by an instanceOf...

we had a method who received a two type parameter

getElement(svc: TypeA | TypeB) {
  svc instanceof TypeA
}

don't really know why... but only worked after removing this

answered Mar 23, 2024 at 13:45

RicardoVallejo

1,13610 silver badges13 bronze badges

Comments

isaac · Accepted Answer · 2020-04-22 06:05:58Z

-6

it caused by capitalized file Name.

Key-store.entity.ts -> key-store.entity.ts

make filename all to lowercase.

answered Apr 22, 2020 at 6:05

isaac

1

Collectives™ on Stack Overflow

Error while running nestjs in production mode, cannot find module

13 Answers 13

4 Comments

6 Comments

Comments

2 Comments

2 Comments

Comments

A solution

1 Comment

1 Comment

Comments

Comments

Comments

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

13 Answers 13

4 Comments

6 Comments

Comments

2 Comments

2 Comments

Comments

A solution

1 Comment

1 Comment

Comments

Comments

Comments

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related