Update gemini model tilda blocks #173
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Новые возможности: - Полный перевод интерфейса на русский язык - Настройка для деплоя на Railway - Добавлены файлы конфигурации Railway Изменения: - app/layout.tsx: переведено описание приложения - app/page.tsx: переведены все сообщения интерфейса, статусы, кнопки - README.md: переведена документация и добавлены инструкции для Railway - .env.example: добавлены комментарии на русском языке Деплой: - railway.json: конфигурация для Railway - RAILWAY_DEPLOY.md: подробные инструкции по деплою Готово к деплою на Railway!
Исправления деплоя: - Обновлена конфигурация railway.json с правильной командой сборки - Добавлен nixpacks.toml для настройки процесса сборки - Удален pnpm-lock.yaml, используется npm - Обновлены инструкции по деплою Решение проблемы: - Исправлена ошибка 'frozen-lockfile' в Railway - Теперь Railway будет использовать npm вместо pnpm - Добавлены точные настройки сборки
Исправления Nixpacks: - Исправлен nixpacks.toml с правильным пакетом nodejs_20 - Упрощена конфигурация railway.json - Удалена специфичная команда сборки Добавлен Dockerfile: - Альтернативный метод деплоя если Nixpacks не работает - Оптимизирован для Node.js 20 Alpine - Railway автоматически выберет лучший вариант Обновлена документация: - Добавлены инструкции по решению проблем Nixpacks - Объяснен выбор между Nixpacks и Docker - Расширен раздел troubleshooting Теперь Railway имеет 2 варианта сборки для надёжности
Исправления зависимостей: - Обновлен package-lock.json для синхронизации с package.json - Исправлены недостающие пакеты (@ai-sdk/google, next-themes, etc.) - Обновлены версии для совместимости Исправления Dockerfile: - Заменен устаревший --only=production на --omit=dev - Изменен порядок: сначала установка всех зависимостей, затем сборка - Добавлено удаление devDependencies после сборки - Добавлена очистка npm cache Обновлен nixpacks.toml: - Изменена команда с 'npm install' на 'npm ci' для стабильности - Использует lockfile для детерминированных сборок Теперь Railway должен собираться без ошибок зависимостей!
Исправления Docker: - Заменен node:20-alpine на node:20-slim для совместимости с lightningcss - Добавлен Dockerfile.extended с системными пакетами (python3, make, g++) - Исправлена ошибка 'Cannot find module lightningcss.linux-x64-musl.node' Обновлен nixpacks.toml: - Добавлены python3 и gcc для компиляции нативных модулей - Поддержка lightningcss и других нативных зависимостей Обновлена документация: - Добавлены инструкции по решению проблем lightningcss - Рекомендации по выбору между Alpine и стандартным Linux - Расширен troubleshooting раздел Решение проблемы: - lightningcss теперь корректно работает в Linux окружении - Railway может использовать любой из Dockerfile вариантов - Поддержка как Nixpacks, так и Docker сборки
- Обновлен postcss.config.mjs: заменен tailwindcss на @tailwindcss/postcss, удален autoprefixer - Обновлены зависимости: [email protected], @tailwindcss/[email protected] - CSS уже использует правильный @import и @theme конфигурацию для v4 - Удален autoprefixer (встроен в TailwindCSS v4) - Исправление ошибок lightningcss native module при деплое на Railway
- Исправлена проблема с Google AI Provider в analyze-edit-intent/route.ts - Исправлена логика выбора modelProvider в generate-ai-code-stream/route.ts - Удалены неопределенные переменные modelMapping и isGPT5 - Исправлен неподдерживаемый параметр maxTokens в streamText - Все типы теперь корректно соответствуют AI SDK API Это должно решить ошибку сборки на Railway: 'Type GoogleGenerativeAIProvider is not assignable to type LanguageModel'
- Добавлены проверки на null для global.sandboxState.fileCache - Исправлен тип targetFiles: string[] вместо any[] - Исправлены дублирующиеся переменные fileCache - Все потенциальные null-доступы теперь безопасны Это должно решить ошибку компиляции TypeScript на Railway
- Заменен неработающий импорт from 'next-themes/dist/types' - Использован ComponentProps<typeof NextThemesProvider> для типизации - Исправлена ошибка компиляции TypeScript на Railway Ошибка: Cannot find module 'next-themes/dist/types'
- Заменен results.filesCreated на data.filesCreated || [] - Исправлена ошибка: Cannot find name 'results' в line 535 - Переменная results используется до объявления Ошибка TypeScript в app/page.tsx:535:39
- Убраны свойства 'edited' из объектов файлов для соответствия типам - Исправлена типизация modelDisplayNames с as keyof - Добавлен Suspense boundary для useSearchParams() - Проект успешно собирается без ошибок - Готов к деплою на Railway Все TypeScript ошибки исправлены
TypeScript нужен в dependencies для загрузки next.config.ts на Railway
- Добавлена правильная настройка портов в next.config.ts - Оптимизированы настройки для serverless deployment - Добавлена поддержка переменной PORT для Railway
- timeoutMinutes: 15 60 в app.config.ts - Теперь sandbox будет работать 1 час вместо 15 минут - Максимальное время по E2B бесплатному плану
- Добавлены два тарифа: Базовый (299, 5 запросов) и Профессиональный (499, 15 запросов) - Красивый дизайн с анимацией и градиентами - Описание возможностей каждого тарифа - Информация о бесплатном хостинге и возможности подключения своего домена - Адаптивная сетка для мобильных устройств
- Install @supabase/supabase-js package - Create Supabase client configuration (lib/supabase.ts) - Add comprehensive helper functions (lib/supabase-helpers.ts) - Add project-specific helpers (lib/supabase-projects.ts) - Create React hooks for Supabase (lib/hooks/useSupabase.ts) - Add example component (components/SupabaseExample.tsx) - Add example API endpoint (app/api/supabase-example/route.ts) - Create initial database schema with migrations - Add TypeScript types (types/supabase.ts) - Add test script (scripts/test-supabase.js) - Create comprehensive documentation: - SUPABASE_SETUP.md (full documentation) - SUPABASE_QUICKSTART.md (quick start guide) - SUPABASE_INTEGRATION_SUMMARY.md (summary) - docs/SUPABASE_CHECKLIST.md (integration checklist) - supabase/README.md (migrations documentation) - Update README.md with Supabase info - Update .env.example with Supabase variables - Add npm script: test:supabase Database schema includes: - profiles table (user profiles) - projects table (AI-generated projects) - project_files table (project files) - generation_history table (code generation history) - RLS policies for all tables - Indexes for performance - Triggers for automation
- Add dynamic rendering to supabase-example route - Use lazy imports to avoid build-time execution - Add placeholder values for Supabase client when env vars not set - Check for Supabase config before executing operations - Suppress warnings during production build
- Create AuthModal component for login/signup - Create UserButton component with dropdown menu - Create AuthContext for global user state management - Create dashboard page with project management - Create PageHeader component with integrated auth - Add AuthProvider to app layout - Create comprehensive AUTH_SETUP.md documentation Features: - Email/password authentication via Supabase - User profile with avatar - Personal dashboard with project statistics - Protected routes (auto-redirect if not authenticated) - Dark mode support - Responsive design - Integration with existing Supabase setup
- Add SiReact to imports in app/page.tsx (fixes build error) - Remove unused UserButton import from app/page.tsx - Remove unused User import from components/auth/UserButton.tsx
- Create HomeScreenHeader component with UserButton - Replace GitHub template button with auth button - Add automatic integration script - Add detailed integration guide (INTEGRATION_GUIDE.md) - Users can now login/register from home screen
- Create database migration with usage tracking tables - Add subscription tiers: free (0), basic (5), professional (15) - Create usage_history and subscription_history tables - Add database functions for limit management: - get_remaining_requests() - increment_usage() - set_subscription_tier() - reset_monthly_usage() - expire_subscriptions() - Create TypeScript library for usage management - Add useUsageLimits React hook - Create UsageLimitBadge component with color indicators - Add API endpoints: - /api/check-usage (GET/POST) - /api/set-subscription (POST) - Add comprehensive documentation (USAGE_LIMITS_SETUP.md) Features: - Real-time usage tracking in Supabase - Automatic limit enforcement - Visual indicators (green/yellow/red) - Server-side validation - Usage history logging - Subscription management
- Add subscription activation in payment webhook - Pass user_id and tier through payment custom fields - Automatically activate subscription after successful payment - Add user authentication check in payment API - Update payment descriptions with request limits - Support both basic (5 requests) and professional (15 requests) tiers
This commit addresses several issues related to incorrect character encoding for Russian (Cyrillic) text in the project.
- The `README.md` and `app/page.tsx` files contained garbled text ("mojibake") due to an incorrect character encoding. They have been corrected to display the Russian text properly.
- The `app/layout.tsx` file has been updated to include the `cyrillic` subset for the 'Inter' font, ensuring that Russian characters render correctly within the application. The 'Space_Grotesk' font was correctly left with only the 'latin' subset as it does not support Cyrillic.
- The `dev` script in `package.json` was modified to remove the `--turbopack` flag. This was done during debugging and helps avoid potential silent failures with the experimental Turbopack bundler, providing clearer error messages.
- The `.env.example` file was re-saved to ensure it uses UTF-8 encoding, as a preventative measure mentioned in `agent.md`.
…ering Fix Cyrillic character encoding and rendering issues
This commit addresses a mojibake issue where Russian text was displayed as garbled characters. The issue was present on the main page and in the user authentication components. - Corrected garbled Russian strings in `app/page.tsx`. - Corrected garbled Russian strings in `components/auth/UserButton.tsx`. Frontend verification was attempted, but persistent issues with the local development server prevented a final visual confirmation of the fix. The server would not start correctly, timing out verification scripts. Both development and production builds were attempted without success.
…ering Fix Russian text encoding issues
This commit addresses a mojibake issue where Russian text was displayed as garbled characters. The issue was present on the main page and in the user authentication components, including the login/signup modal. - Corrected garbled Russian strings in `app/page.tsx`. - Corrected garbled Russian strings in `components/auth/UserButton.tsx`. - Corrected garbled Russian strings in `components/auth/AuthModal.tsx`. Frontend verification was attempted, but persistent issues with the local development server prevented a final visual confirmation of the fix. The server would not start correctly, timing out verification scripts. Both development and production builds were attempted without success.
This commit addresses a mojibake issue where Russian text was displayed as garbled characters. The issue was present on the main page and in the user authentication components, including the login/signup modal. - Corrected garbled Russian strings in `app/page.tsx`. - Corrected garbled Russian strings in `components/auth/UserButton.tsx`. - Corrected garbled Russian strings in `components/auth/AuthModal.tsx`. Frontend verification was attempted, but persistent issues with the local development server prevented a final visual confirmation of the fix. The server would not start correctly, timing out verification scripts. Both development and production builds were attempted without success.
…ering Fix Russian text encoding issues
This commit addresses a mojibake issue where Russian text was displayed as garbled characters. The issue was present on the main page, in the user authentication components (including the login/signup modal), and on the user dashboard page. - Corrected garbled Russian strings in `app/page.tsx`. - Corrected garbled Russian strings in `components/auth/UserButton.tsx`. - Corrected garbled Russian strings in `components/auth/AuthModal.tsx`. - Corrected garbled Russian strings in `app/dashboard/page.tsx`. Frontend verification was attempted, but persistent issues with the local development server prevented a final visual confirmation of the fix. The server would not start correctly, timing out verification scripts. Both development and production builds were attempted without success.
…ering Fix Russian text encoding issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.