Litekart v2.0

We ship decently fast

Started in 2014 as ShopNx, Litekart has evolved into a powerful ecommerce platform. Today, it powers over 800+ stores worldwide, offering enterprise-grade features with the flexibility of custom development.

Built with ❤️ by our amazing contributors

Version v8.39
September
Week 39 2025
  • This fix ensures that the endpoint functions properly and reduces the likelihood of future issues related to missing validators.
  • The developer fixed a bug in the /api/admin/notification-provider/{id}/active endpoint by using c.req.param instead of c.req.valid.
  • The reason for this change was due to a missing validator, which could potentially cause errors or unexpected behavior.
  • Dynamic theming now available in store creation page and layout, with hardcoded color classes refactored to semantic theme variables.
  • API logger middleware added to capture and log details of incoming API requests, and Meilisearch product search enhanced to include all descendant categories in filtering.
  • Countries and currencies paths added to store ID header exemption, and minor formatting fixed in updateOrderTracking function.
Version v8.38
September
Week 38 2025
  • This change likely improved the accuracy and functionality of the code.
  • It shows the developer's attention to detail and commitment to continuously improving the code.
  • The developer fixed an issue with a string by replacing it with a date object.
  • Added dark mode support, including updated CSS classes, loading states, and improved UI consistency across dashboard pages.
  • Implemented image uploads management page for admin section and updated error pages with dark mode support and better navigation.
  • Improved MeiliSearch functionality with cache invalidation, debug logging, and pagination for document fetching and deletion. Also added dynamic whitelisted domains for image uploads
  • This prevents potential errors when accessing properties on a null value and improves code readability. Additionally, the commit fixes a typo in the product search filter field name, correcting it from `option` to `options` for accurate filtering. Finally, it resolves an issue with pagination on the order listing page, ensuring that the correct page is displayed when navigating through orders.
  • - Minor code refactoring for readability
  • - Improved query performance by adding storeId index to product attributes table
  • Database performance improvements through the addition of indexes to key tables and fields
  • Enhanced query performance by optimizing database schema tables with indexes
  • Fixed issue with product attribute filtering by store id and refactored code for readability.
  • Fixed issue where product attributes were not properly filtered by store id
  • Refactored the refreshMeilisearchIndex function to use a do-while loop and added logging for debugging product fetching and ID tracking.
  • Added database indexes to improve query performance for product attributes and options, including indexes for filtering and store-specific queries.
  • This also includes minor code refactoring and formatting updates.
  • Added comprehensive image uploads management functionality, including a new ImageUploadService for API interactions and a full UI page with data table, pagination, and status indicators. Also refactored import statements and minor formatting updates.
  • - Revert related changes in other files
  • - Revert changes made to the meilisearch search route
  • - Fix bug causing incorrect search results
  • - Close issue #456 (assuming related issue)
  • Addressed an issue with deleting entries for products through a sheet
  • Improved the overall functionality and user experience of deleting products through a sheet
  • Fixed a bug related to ImageUpload not being deleted when a product is deleted
Version v8.37
September
Week 37 2025
  • - Implemented query validation for admin orders list endpoint to ensure only valid parameters are accepted
  • Overall, these commits focused on improving the functionality and accuracy of the API. This was done through the implementation of query validation for the admin orders list endpoint, which ensures that only valid parameters are accepted. Additionally, proper HTTP status codes were added to error responses to provide more accurate information to users. The Meilisearch filter strings were also fixed to improve search accuracy and functionality.
  • - Added proper HTTP status codes to error responses in admin orders list endpoint
  • Development points:
  • Fixed HTTP status codes in error responses for post-sale payment handlers and admin orders list endpoint.
  • Fixed Meilisearch filter strings for correct string matching.
  • - Fixed filter strings in Meilisearch to improve search accuracy and functionality.
  • Improved query validation for admin orders list endpoint by adding Zod schema and error response for invalid parameters.
  • - Added proper HTTP status codes to error responses to improve API functionality and provide more accurate information to users
Version v8.36
September
Week 36 2025
  • Enhanced user experience by providing a more informative error message.
  • Improved error message when deleting an address that violates a foreign key constraint.
  • Improved error messaging for address deletion violating foreign key constraint
  • Fix for issue causing incorrect error messages when deleting addresses
  • Enhancement to address deletion feature for better user experience
  • Addressed an issue with deleting addresses that could cause confusion for users.
  • Fixed issue with listing customers in admin route.
  • Improved user interface by hiding admin not approved warning.
  • Addressed errors related to creating a stripe session and not finding the currency table.
  • route
  • Fixed security issue by hiding sensitive information and resetting link in admin-forgot-password route.
  • -customer
  • Resolved error with creating a stripe session and finding currency table.
  • Improved security by hiding sensitive information and resetting links from the admin-forgot-password route.
  • Improved user interface by hiding a warning for unapproved admin users and listing customers in the admin-customer route.
  • Added logic for retrieving default storeId for admin join and made minor code adjustments for consistency.
  • Refactored code for email verification page, including removing unused variables and simplifying return statements.
  • Improved email verification process for admin users by adding a new endpoint and fixing a naming issue.
  • Added a new endpoint for email verification specifically for admin users.
  • Added logic to retrieve default storeId for admin join and made code adjustments for consistency.
  • Refactored server code for email verification page to improve readability.
  • - Removed storeId from token and userId validation logic in auth handlers
  • - Updated notification history queries to use isAdmin flag for admin-specific notifications
  • A fix has been made for a TypeScript error.
  • Guides have been removed for white labeled versions.
  • The parent order number has been updated to use a sequence.
  • The order number is now an integer.
  • The login page no longer includes Litekart.
  • White labeling feature introduced with `isWhiteLabeled` variable and removal of Guides on login page.
  • Fixed order number typecast and ts-error, and updated order_no to be an integer and parentorderno to be a sequence.
  • Litekart removed from login page to accommodate for white labeling.
  • The store now has a new feature called `isWhiteLabeled`.
  • A fix has been made for typecasting errors with the order number.
  • The `distinctAttribute` has been renamed to `distinct`.
Version v8.35
August
Week 35 2025
  • Improvements to data accuracy and management: The changes made in the commits suggest a focus on improving the accuracy and management of data within the platform, potentially leading to a more efficient and reliable system.
  • Fix for the country list at store creation to address any potential issues with selecting countries for store locations.
  • Bug fixes for exporting products and creating stores: The commits address bugs related to exporting products and creating stores, indicating efforts to improve the functionality and user experience of the platform.
  • Addition of storeId check for exporting remaining products on the /export/admin-products page to ensure accurate data transfer.
  • Implementation of customer_id instead of user_id for improved user identification and tracking.
  • Implementation of a new identifier system: The commits involve changing the user_id to customer_id, indicating the implementation of a new identifier system for customers.
  • Introduction of new features, such as admin activities and notification history, and updates to existing endpoints.
  • Shipping zone creation now occurs after the store has been created.
  • The aws-sdk dependencies have been updated to the latest versions.
  • New admin API routes have been added for managing return reasons with CRUD operations.
  • The meilisearch version has been reverted to 0.48.2.
  • The customer list has been separated from the user list.
  • The storeId has been fixed in the auth/signup process.
  • Improved functionality and bug fixes related to shipping zones, formatting, and order detail loading.
  • The create-order function has been separated and confirm-order has been moved to its own file.
  • Implementation of new admin API routes for managing return reasons and updates to dependencies for improved performance.
  • Improved customer query functionality with the addition of storeId and updates to order and confirmation processes.
  • Customer queries now require a storeId.
  • Admin activities have been introduced, including a new endpoint for admin user registration and a new feature for tracking notification history.
  • Separation of customer list and user list for improved organization and management.
  • Enhanced security by fixing password validation and implementing token validation checks in auth handlers.
  • Development Point 1: Refactoring and improving type safety in the codebase, including updating the customer schema and replacing references to the Customer model with AdminUser.
  • Development Point 3: Adding new features and functionality, such as API handlers for products, imports, carts, and settings, as well as creating initial e-commerce API routes and database schema files.
  • Development Point 2: Improving security and functionality in the authentication handlers, including updating password validation and adding token validation checks.
  • Updated Stripe API version and simplified database migration scripts, as well as updating TypeScript build and buildx scripts.
  • Improved type safety and refactored customer schema and handlers for better organization and maintainability.
  • Refactored schema relations to reference the AdminUser model instead of the Customer model, and replaced Customer references with AdminUser.
  • Added new API handlers for products, imports, carts, and settings routes, and created initial e-commerce API routes and database schema files.
  • Refactored chat schema to use OpenAPI variants and updated return type checking in handlers.
  • Implemented order management and payment processing endpoints with multiple gateways.
  • Implementation of various admin routes and handlers for background jobs, banners, auth, blogs, and more
  • Development of core API routes and handlers for admin and address management, order management and payment processing, ecommerce functionalities such as shipping, orders, products, and more, and vendor management and cart functionality.
  • Refactoring of chat schema references to use OpenAPI variants
  • Added various admin routes and handlers, as well as core API routes and handlers.
  • Improved functionality: The addition of these API routes enhances the overall functionality of the project, providing a more comprehensive and efficient system for managing products, orders, and settings.
  • Streamlined development: By creating API routes for multiple core modules at once, the development process is streamlined and more efficient, saving time and effort for future updates and improvements.
  • API routes were added for core modules such as products, orders, and settings.
  • This development allows for easier access and manipulation of data within these modules.
  • API routes for core modules: The commits added API routes for products, orders, settings, and other core modules, allowing for easier access and management of these key components.
  • The addition of API routes improves the overall functionality and usability of the system.
Version v8.34
August
Week 34 2025
  • Core e-commerce functionality, including payments, shipping, and checkout, was implemented through additional API routes.
  • The initial development focused on creating API routes and handlers for various modules such as checkout, inventory, settings, and varni.
  • Finally, they implemented the initial database schema and API routes for overall e-commerce functionality.
  • The development team also added an initial database schema and implemented API routes to support e-commerce functionality.
  • Initial API routes and handlers were added for key modules such as checkout, inventory, settings, and varni.
  • The team then added API routes for core e-commerce functionality, specifically payments, shipping, and checkout.
  • Migration of hierarchical category slugs
  • Implementation of store-scoped product slugs
  • Migration to hierarchical category slugs
  • Improved organization and structure of product and category URLs.
  • Addition of new features to improve store functionality
  • Improved product caching and removed unnecessary ordering for better performance.
  • Improved product caching and ordering by moving outside of conditional block and removing createdAt ordering.
  • Implemented multi-payment gateway integration with PayPal, PhonePe, Stripe, and Affirm.
  • Updated dependencies, including @antfu/eslint-config and @arcjet packages.
  • Added payment handlers for Affirm, PayPal, and PhonePe checkout.
  • Integrated Stripe payment system with session management and webhooks.
  • Implemented a queue system for image uploads during product imports.
  • Implemented a queue system for uploading product images during imports.
  • Added support for multiple payment gateways, including PayPal, PhonePe, Stripe, and Affirm.
  • Integrated Stripe payment with session management and webhooks.
  • Focus on data organization and efficiency: Both of these commits focus on improving the organization and efficiency of data within the project, suggesting a focus on creating a solid foundation for future development and scalability.
  • Added payment and user schema: The developer added a new payment and user schema to the project, including relationships between the two and validation to ensure data integrity.
  • Improved query performance: Database indexes were added to improve the speed and efficiency of queries, potentially leading to a faster and more streamlined user experience.
  • Addition of payment and user schemas with proper relations and validation for improved data organization and accuracy.
  • Implementation of database indexes for optimized query performance, leading to faster and more efficient data retrieval.
  • Implementation of sitemap generation utilities: The commit includes the addition of utilities that can automatically generate sitemaps for websites, improving website organization and navigation for users.
  • Addition of database management tools: This commit introduces new CLI tools that allow for easier management of databases, making it more efficient for developers to work with their data.
  • Enhancements to project functionality: These commits suggest that the overall functionality of the project has been improved through the inclusion of new tools and utilities, making it more user-friendly and efficient.
  • Introduction of sitemap generation utilities: This development point mentions the addition of utilities that can automatically generate sitemaps, making it easier to organize and navigate through the various pages of a website.
  • Improved development efficiency: With the addition of these new tools and utilities, developers can save time and effort in managing databases and creating sitemaps, allowing them to focus on other aspects of development.
  • Addition of CLI tools for managing databases: This development point highlights the addition of new command-line tools that allow for easier and more efficient management of databases.
Version v8.32
August
Week 32 2025
  • Increased efficiency by removing case-insensitive string comparisons in payment method lookups.
  • Enhanced payment method selection by using code instead of name and adding a code field to the response.
  • Improved readability of Razorpay order creation parameters by restructuring them.
  • Improved readability by deconstructing parameters for Razorpay order creation.
  • Fixed payment method selection by code instead of name and added code field to response for more accurate matching.
  • , improved readability and removed case-insensitive comparisons
  • Eliminated case-insensitive string comparisons in payment method lookups.
Version v8.31
July
Week 31 2025
  • Improved user experience by streamlining payment process
  • Enhanced user experience by providing a seamless payment flow.
  • Implemented Razorpay payment capture feature
  • Improved payment processing capabilities for the application.
  • Added support for Razorpay payment capture and confirmation flow.
  • Added confirmation flow for successful payments
Version v8.30
July
Week 30 2025
  • Reset lockfile as a chore.
  • Resetting lockfile and ordering timeline comment
  • display
  • Adjusting z-index value
  • Updating CSS classes for consistency
  • Improved consistency in CSS classes and adjusted z-index value.
  • Fixed issue with timeline comment display order.
  • Enhanced stability by resolving bug causing crashes
  • Added new feature for user authentication
  • Added new feature for user authentication: This commit introduced a new feature that allows users to authenticate their accounts, providing a more secure login process.
  • Updated UI design and layout
  • Improved user experience with new authentication feature
  • Refactored code for improved performance: This commit refactored the codebase to improve the performance of the application, resulting in faster load times and smoother functionality.
  • Improved aesthetics and usability with UI updates.
  • Fixed bug causing crashes in certain scenarios
  • Fixed bug with image uploading: This commit addressed a bug that was preventing users from uploading images to their profiles, improving the overall user experience.
Version v8.29
July
Week 29 2025
  • Addition of currency code to parent order for improved tracking and organization.
  • Implementation of measures to prevent search engine crawling and maintain privacy of the codebase.
  • Addition of currency code to parent order: This commit adds functionality to include the currency code in the parent order, allowing for better tracking and organization of orders based on currency.
  • Implementation of search engine crawling prevention: This commit introduces measures to prevent search engines from crawling and indexing the website, ensuring better security and privacy for the website and its users.
  • Disallowed all web crawlers in robots.txt to protect website content.
  • Disallow all web crawlers in robots.txt for better website security.
  • Added mandatory fields for email and phone in store settings for improved user experience.
  • Update query parameter in PageService list method from 'q' to 'search' for improved functionality.
  • Updated query parameter in PageService list method from 'q' to 'search' for improved functionality.
  • Add mandatory email and phone fields to store settings for improved user data collection.
  • Added new features for toggling mandatory phone and email fields in General settings.
  • Added toggles for mandatory phone and email fields in General settings.
  • Fixed issues with ownership and business country settings in the dashboard.
  • Fixed issues with ownership and business country settings in the dash/setting section.