\n\n## Description\n\nQdrant module for [Nest](https://github.com/nestjs/nest) based on the official [@qdrant/js-client-rest\n](https://www.npmjs.com/package/@qdrant/js-client-rest) package.\n\n## Installation\n\n```bash\n$ npm i --save @bytebitlabs/nest-qdrant @qdrant/js-client-rest\n\n```\n\n## Usage\n\nImport `QdrantModule`:\n\n```typescript\n@Module({\n imports: [QdrantModule.register({\n url: 'http://127.0.0.1:6333',\n })],\n providers: [...],\n})\nexport class VectorStoreModule {}\n```\n\nInject `QdrantService`:\n\n```typescript\n@Injectable()\nexport class VectorStoreService {\n constructor(private readonly qdrantService: QdrantService) {}\n}\n```\n\n## Async options\n\nQuite often you might want to asynchronously pass your module options instead of passing them beforehand. In such case, use `registerAsync()` method, that provides a couple of various ways to deal with async data.\n\n**1. Use factory**\n\n```typescript\nQdrantModule.registerAsync({\n useFactory: () => ({\n url: 'http://127.0.0.1:6333'\n })\n});\n```\n\nObviously, our factory behaves like every other one (might be `async` and is able to inject dependencies through `inject`).\n\n```typescript\nQdrantModule.registerAsync({\n imports: [ConfigModule],\n useFactory: async (configService: ConfigService) => ({\n url: configService.get('QDRANT_URL'),\n }),\n inject: [ConfigService],\n}),\n```\n\n**2. Use class**\n\n```typescript\nQdrantModule.registerAsync({\n useClass: QdrantConfigService\n});\n```\n\nAbove construction will instantiate `QdrantConfigService` inside `QdrantModule` and will leverage it to create options object.\n\n```typescript\nclass QdrantConfigService implements QdrantOptionsFactory {\n createQdrantOptions(): QdrantModuleOptions {\n return {\n url: 'http://127.0.0.1:6333'\n };\n }\n}\n```\n\n**3. Use existing**\n\n```typescript\nQdrantModule.registerAsync({\n imports: [ConfigModule],\n useExisting: ConfigService,\n}),\n```\n\nIt works the same as `useClass` with one critical difference - `QdrantModule` will lookup imported modules to reuse already created `ConfigService`, instead of instantiating it on its own.\n\n## API Spec\n\nThe `QdrantService` wraps the `QdrantClient` from the official [@qdrant/js-client-rest\n](https://www.npmjs.com/package/@qdrant/js-client-rest) methods. The `QdrantModule.register()` takes `options` object as an argument, [read more](https://qdrant.tech/documentation/quickstart/).\n","readmeFilename":"README.md"}
![\"ByteBitLabs](\"https://gravatar.com/avatar/61c80d73dfe4c4231e77940cf80fd410?size=256\")
![\"NPM](\"https://img.shields.io/npm/v/@bytebitlabs/nest-qdrant\")
![\"Package](\"https://img.shields.io/npm/l/@bytebitlabs/nest-qdrant\")
![\"NPM](\"https://img.shields.io/npm/dm/@bytebitlabs/nest-qdrant\")