- Removed `randombytes` and `safe-buffer` from package-lock.json as they are no longer needed.
- Updated `serialize-javascript` to version 7.0.3 in both package.json and package-lock.json to ensure compatibility with Node.js 20.0.0 and above.
- Adjusted overrides and resolutions in package.json to reflect the updated version of `serialize-javascript`.
These changes streamline the dependency management and ensure the project is using the latest compatible versions of critical packages.
- Added a new `.env.lite.example` file for the Lite version, providing a minimal configuration template.
- Updated `.env.example` to remove deprecated variables and include new Docreader settings.
- Enhanced Docker configurations to support the Lite version, including a new Dockerfile for the Docreader service.
- Introduced a Makefile target for building and running the Lite version, along with packaging capabilities.
- Created GitHub workflows for building and releasing Lite binaries, including Homebrew formula support.
- Implemented a new service file for managing the Lite version as a system service.
This update enables a streamlined, single-binary deployment of WeKnora, reducing external dependencies and simplifying setup.
- Added support for tracking the status of FAQ import tasks, including progress indicators for ongoing imports.
- Introduced new localization strings for processing tasks and batch operations in multiple languages.
- Updated the FAQ entry manager to display import progress and improved user feedback during the import process.
- Enhanced the KnowledgeBase component to reflect the processing state of knowledge items, improving user experience during document uploads.
- Implemented batch deletion functionality for chunks, streamlining the management of knowledge base content.
- Updated the xlsx package version from 0.18.5 to 0.20.2 in both package.json and package-lock.json.
- Changed the resolution method for xlsx to use a local tarball instead of a remote source.
- Added support for creating and managing FAQ knowledge bases, including new API endpoints for listing, upserting, updating, and deleting FAQ entries.
- Enhanced the frontend to allow users to create FAQ knowledge bases and manage FAQ entries with a dedicated interface.
- Introduced new types and configurations for FAQ handling in the backend, ensuring proper indexing and retrieval of FAQ entries.
- Updated localization files to include new strings related to FAQ management in multiple languages.
- Refactored existing components to accommodate the new FAQ features, improving user experience and functionality.
- Added vue-i18n integration to various components for dynamic text translation.
- Updated text placeholders, button labels, and error messages to utilize translation functions.
- Enhanced user experience by providing localized content in the Knowledge Base, chat components, and settings.
- Removed hardcoded strings and replaced them with translation keys for better maintainability and scalability.
- Added Swiper library to package dependencies for improved UI components.
- Updated chat API to include summary model ID in message handling, allowing for more flexible model selection.
- Enhanced InputField component to manage model selection and state more effectively.
- Improved event handling in chat components to support new model features and ensure accurate message processing.
- Refactored SVG assets for better visual consistency and updated styles for improved user experience.
- Upgraded tdesign-vue-next to version 1.17.2 for improved features and performance.
- Replaced emoji icons with corresponding tdesign icons in UserMenu and Settings components for consistency.
- Adjusted styles in the nav-icon class for better alignment and visual appeal.
* feat: add multilingual support (English and Russian)
- Add i18n infrastructure with vue-i18n
- Implement language switcher component
- Add Russian (ru-RU) and English (en-US) translations
- Configure TDesign locale for proper UI component translation
- Replace hardcoded Chinese strings with i18n keys
- Support dynamic language switching in all components
- Add translations for all UI elements including:
- Menu items and navigation
- Knowledge base management
- Chat interface
- Settings and initialization
- Authentication pages
- Separator options in document splitting
This enables users to use the application in Chinese, English, or Russian.
* chore: add vue-i18n dependency and fix Input-field i18n integration
- Add vue-i18n package to frontend dependencies
- Fix Input-field component i18n integration for multilingual support
* chore: add PROGRESS_RU.md to .gitignore
- Exclude personal progress tracking file from git
* rearrange the order of the multilingual languages: Chinese, English, Russian
* Delete docker-compose.yml
* Replaced hardcoded messages with the t() function in the following files: all error messages, 14 console.error ,messages session creation messages
, login/registration errors
* fix: restore docker-compose.yml and update .gitignore
* restore docker-compose.yml latest
* add multilingual support
wizardchen