Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Node.js, PHP and APIs

Nest can't resolve a dependency such as DataSource or a repository

ErrorNest can't resolve dependencies of the UsersService (?). Please make sure that the argument DataSource at index [0] is available in the UsersModule context.

Short answer

Nest builds each module on its own. The error means the module that owns the failing class has no provider for the token in the message. Turn on NEST_DEBUG, read the module and index it names, then register the provider, import the module that exports it, or export it from where it lives.

  • Applies to NestJS 11, @nestjs/typeorm 11, TypeORM 0.3, Node.js 22
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Run the app with Nest's dependency logging on, and read the module name and index in the message. They tell you which module needs the fix.

    NEST_DEBUG=1 npm run start
  2. 2Match what you see, then jump to its fix

    1. 1Please make sure that the argument <name> at index [<n>] is available in the <Module> moduleThe provider is not registered or not exported in a module the failing class can seeFix
    2. 2Nest reports that the class cannot appear in the imports arrayA class is listed in imports instead of providersFix
    3. 3The message has no token name: argument at index [0] is available in the current moduleThe token is undefined at runtime because two files import each otherFix
    4. 4The message has no token name, and the constructor parameter is an interface or imported with import typeAn interface or a type-only import is used as the injection tokenFix

What does the error look like?

  • Nest can't resolve dependencies of the UsersService (?). Please make sure that the argument DataSource at index [0] is available in the UsersModule context.
  • Please make sure that the argument at index [0] is available in the current module.

Cause 1 of 4

The provider is not registered or not exported in a module the failing class can see

1Check

The token must be in the module's providers, or exported by a module listed in its imports. For a TypeORM repository, the module needs TypeOrmModule.forFeature with the entity.

grep -rn "forFeature\|providers:\|exports:" src --include=*.module.ts

2Fix

Register the repository in the module that injects it. To share it with other modules, export what forFeature generates and import that module there.

@Module({
  imports: [TypeOrmModule.forFeature([User])],
  providers: [UsersService],
  exports: [TypeOrmModule],
})
export class UsersModule {}

3Verify

The app boots without the resolution error.

npm run start

Confirmed by docs.nestjs.com

Did this fix it?

Cause 2 of 4

A class is listed in imports instead of providers

1Check

Search the failing module for an @Injectable class inside its imports array.

grep -n -A6 "imports:" src/users/users.module.ts

2Fix

Move the class to providers. Only modules belong in imports.

@Module({
  imports: [TypeOrmModule.forFeature([User])],
  providers: [UsersService],
})
export class UsersModule {}

3Verify

Start the app again.

npm run start

Confirmed by docs.nestjs.com

Did this fix it?

Cause 3 of 4

The token is undefined at runtime because two files import each other

1Check

Two files import each other, for example a module file that exports a constant a service imports. Barrel index.ts files can create the same loop.

npx madge --circular --extensions ts src

2Fix

Break the import loop. Move shared constants or tokens into a separate file that imports nothing from the modules.

// src/users/users.constants.ts
export const USERS_TOKEN = 'USERS_TOKEN';

3Verify

The check reports no cycle and the app starts.

npx madge --circular --extensions ts src
npm run start

Confirmed by docs.nestjs.com

Did this fix it?

Cause 4 of 4

An interface or a type-only import is used as the injection token

1Check

Interfaces do not exist at runtime, and import type removes the class. Nest sees undefined or Object.

grep -rn "import type" src

2Fix

Inject the class itself with a normal import, or use a string, Symbol or abstract class token with @Inject().

constructor(@Inject('CONNECTION') private connection: Connection) {}

3Verify

The app starts and the service receives its dependency.

npm run start

Confirmed by docs.nestjs.com

Did this fix it?

How do I stop it coming back?

  • Give every feature module its own forFeature call and export only what other modules need.
  • Keep tokens and constants in files that do not import modules or services.
  • Run the app in CI so a missing provider fails the build, not production.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Back end

NestJS GraphQL cannot work out the output type of a field or query

Cannot determine a GraphQL output type for the "<name>". Make sure your class is decorated with an appropriate decorator.

In code-first mode Nest reads TypeScript types through decorators, and arrays, promises and unions disappear at runtime.

2 causes, each with a fix

Back end

IntelliJ IDEA breakpoints are ignored in a NestJS app

No 'Debugger listening' line appears when the NestJS app starts

IntelliJ can only debug a NestJS app when the Node.js process runs with the inspector on and the IDE attaches to its port.

4 causes, each with a fix

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.