- Introduced a new skill for frontend design, emphasizing distinctive and production-grade UI creation.
- Added detailed guidelines for design thinking, aesthetics, and implementation best practices.
- Included a LICENSE file for the skill and updated README with development environment recommendations.
- Simplified the plugin definition by removing the nitroApp parameter.
- Consolidated the interval and timeout setup for syncing feeds into a more concise format.
- Changed DATABASE_URL in .env.example to use SQLite file.
- Modified refresh function calls in AppShell.vue and public.vue to remove unnecessary parameter.
- Enhanced run.sh to include seeding script execution.
- Improved seed.js to ensure proper SQLite file path resolution and directory creation.
- Introduced db-bun.ts for Bun compatibility with SQLite.
- Updated db.ts to handle better-sqlite3 integration and path management.
- Adjusted paths.ts to ensure reliable package root resolution for production.
- Added site name configuration to global settings.
- Improved public home layout with dynamic header and navigation.
- Introduced detailed view for posts and timeline with visibility controls.
- Implemented admin interface for site configuration management.
- Enhanced user experience with responsive design adjustments and improved loading states.
Replace session ID retrieval and validation logic with a direct call to requireUser() for improved clarity and efficiency in user authentication. This change streamlines the error handling process by ensuring that session cookies are cleared only when necessary.
Enhance the environment configuration for the SQLite database by adjusting the handling of the DATABASE_URL to ensure correct file path resolution based on the NODE_ENV variable. Modify the temporary working directory logic to correctly set paths for both production and development environments, improving overall path management.
Modify the temporary working directory path in the SQLite database configuration to dynamically set the current working directory based on the NODE_ENV variable. This change ensures that the application uses the correct path in both production and development environments.
Transition the database from PostgreSQL to SQLite, updating migration files, database connection settings, and schema definitions accordingly. Adjust package dependencies to reflect the new database type and ensure compatibility. Remove obsolete migration files and snapshots related to PostgreSQL. Enhance error handling in authentication and configuration services to accommodate the new database structure.