Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nest cant resolve dependencies of the RedisLockService #6

Open
talah221 opened this issue Nov 2, 2021 · 3 comments
Open

Nest cant resolve dependencies of the RedisLockService #6

talah221 opened this issue Nov 2, 2021 · 3 comments

Comments

@talah221
Copy link

talah221 commented Nov 2, 2021

Nest can't resolve dependencies of the RedisLockService (?, REDIS_LOCK_OPTIONS). Please make sure that the argument RedisService at index [0] is available in the RedisLockModule context.

Potential solutions:

  • If RedisService is a provider, is it part of the current RedisLockModule?

  • If RedisService is exported from a separate @module, is that module imported within RedisLockModule?
    @module({
    imports: [ /* the Module containing RedisService */ ]
    })

    "@nestjs/common": "^8.1.1",
        "nestjs-redis": "git+https://github.com/skunight/nestjs-redis.git",
    

    "nestjs-simple-redis-lock": "^0.2.1",
    "@huangang/nestjs-simple-redis-lock": "^0.5.0",

tried both importing the redisLockService from @huangang and from nestjs-simple-redis-lock.

@tabyouto
Copy link

same problem.

[Nest] 42092  - 02/23/2022, 1:38:52 PM   ERROR [ExceptionHandler] Nest can't resolve dependencies of the RedisLockService (?). Please make sure that the argument REDIS_LOCK_OPTIONS at index [0] is available in the TaskModule context.

Potential solutions:
- If REDIS_LOCK_OPTIONS is a provider, is it part of the current TaskModule?
- If REDIS_LOCK_OPTIONS is exported from a separate @Module, is that module imported within TaskModule?
  @Module({
    imports: [ /* the Module containing REDIS_LOCK_OPTIONS */ ]
  })

Error: Nest can't resolve dependencies of the RedisLockService (?). Please make sure that the argument REDIS_LOCK_OPTIONS at index [0] is available in the TaskModule context.

Potential solutions:
- If REDIS_LOCK_OPTIONS is a provider, is it part of the current TaskModule?
- If REDIS_LOCK_OPTIONS is exported from a separate @Module, is that module imported within TaskModule?
  @Module({
    imports: [ /* the Module containing REDIS_LOCK_OPTIONS */ ]
  })

@georgemarkosian
Copy link

same problem

@hrishikeshdkakkad
Copy link

How do we fix this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants