A misconfigured embeddings endpoint failed the RAG indexer with an opaque "Invalid JSON response" and was not caught by "Test connection" (which only probed the chat model), so it only surfaced silently during background indexing. - add describeProviderError(): formats AI SDK errors as "<statusCode>: <message> | response body: <truncated one-line snippet>" (statusCode/message/responseBody never carry the API key) - use it in the bulk-reindex catch and the embedding processor's formatter so the real cause (e.g. an HTML 404 from a wrong base URL) is visible in logs - testConnection now probes chat AND embeddings independently: skips a probe when that capability is unconfigured, returns ok:false with a Chat:/Embeddings: prefix on real failure, "not configured" when neither is set
A progressive Node.js framework for building efficient and scalable server-side applications.
Description
Nest framework TypeScript starter repository.
Installation
$ npm install
Running the app
# development
$ npm run start
# watch mode
$ npm run start:dev
# production mode
$ npm run start:prod
Migrations
# This creates a new empty migration file named 'init'
$ npm run migration:create --name=init
# Generates 'init' migration file from existing entities to update the database schema
$ npm run migration:generate --name=init
# Runs all pending migrations to update the database schema
$ npm run migration:run
# Reverts the last executed migration
$ npm run migration:revert
# Reverts all migrations
$ npm run migration:revert
# Shows the list of executed and pending migrations
$ npm run migration:show
## Test
```bash
# unit tests
$ npm run test
# e2e tests
$ npm run test:e2e
# test coverage
$ npm run test:cov
Support
Nest is an MIT-licensed open source project. It can grow thanks to the sponsors and support by the amazing backers. If you'd like to join them, please read more here.
Stay in touch
- Author - Kamil Myśliwiec
- Website - https://nestjs.com
- Twitter - @nestframework
License
Nest is MIT licensed.