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.41
October
Week 41 2025
  • Resolved an issue that was causing inconvenience for users on the dash/customer/[id] page.
  • Improved functionality and user experience on dash/customer/[id] page
  • Increased efficiency and accuracy in retrieving customer information on dash/customer/[id] page
  • Fixed issue with fetching order before customer in dash/customer/[id] page
  • Fixed a bug where the order was being fetched before the customer, causing errors in the dash/customer/[id] page.
  • Improved the functionality of the dash/customer/[id] page by ensuring the correct order of data retrieval.
Version v8.40
October
Week 40 2025
  • Improved functionality and efficiency for managing category data.
  • Added new API endpoint to fetch details of all categories at once
  • Added new endpoint for fetching details of all categories at once
  • Improved efficiency and functionality of the API.
  • Fixed issue with getAllDescendantSlugs function
Version v8.40
October
Week 40 2025
  • Added cache clearing functionality for product removal operations
  • Development Points:
  • Prevention of serving stale cached data to clients.
  • Expanded cache clearing to include various data types
  • Addition of cache clearing functionality for product removal operations
  • Clearing of various caches to ensure data freshness
  • Ensured data freshness and prevented serving stale cached data to clients.
Version v8.39
September
Week 39 2025
  • A bug in the code was fixed in the "/api/admin/notification-provider/{id}/active" endpoint.
  • 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 bug was likely causing issues with validating user input and has been resolved to ensure proper functionality.
  • This fix ensures that the endpoint functions properly and reduces the likelihood of future issues related to missing validators.
  • Bug fix: Changed the method for accessing a specific notification provider's active status due to a missing validator.
  • The fix involved using "c.req.param" instead of "c.req.valid" due to a missing validator.
  • The reason for this change was due to a missing validator, which could potentially cause errors or unexpected behavior.
  • Improved validation: Utilized c.req.param instead of c.req.valid to ensure proper validation of notification provider IDs.
  • An API logger middleware was added to capture and log details of incoming API requests, and the Meilisearch product search was enhanced to include all descendant categories in filtering.
  • Added dynamic theming to store creation page and layout, using semantic theme variables and ModeWatcher for automatic dark/light mode switching.
  • Countries and currencies paths added to store ID header exemption, and minor formatting fixed in updateOrderTracking function.
  • Exempted '/api/countries' and '/api/currencies' from store ID header validation and fixed minor formatting in updateOrderTracking function.
  • Added new API logger middleware and enhanced Meilisearch product search to include all descendant categories in filtering and optimize the category data query.
  • 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.
  • The '/api/countries' and '/api/currencies' paths were added to the list of paths exempt from store ID header validation, and a minor formatting issue was fixed in the updateOrderTracking function.
  • Dynamic theming now available in store creation page and layout, with hardcoded color classes refactored to semantic theme variables.
  • Dynamic theming was enabled in the store creation page and layout, with hardcoded color classes being replaced with semantic theme variables.
Version v8.38
September
Week 38 2025
  • Bug fix: Replaced string with date object to improve accuracy and functionality.
  • 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.
  • Code improvement: Implemented date object for more efficient and reliable code.
  • Quality improvement: Enhanced user experience by fixing date-related issue.
  • The developer fixed an issue with a string by replacing it with a date object.
  • Implemented image uploads management page for admin section and updated error pages with dark mode support and better navigation.
  • 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.
  • Implemented image processing enhancements for product imports, including immediate thumbnail setting and bulk processing for non-whitelisted images, as well as comprehensive logging and refactored image upload logic.
  • Added dark mode support to various components and pages, including loading states and improved UI consistency across dashboard pages.
  • Added dark mode support, including updated CSS classes, loading states, and improved UI consistency across dashboard pages.
  • Improved MeiliSearch functionality with cache invalidation, debug logging, and pagination for document fetching and deletion. Also added dynamic whitelisted domains for image uploads
  • Improved MeiliSearch functionality, including cache invalidation, debug logging, pagination for document fetching, and deletion of outdated documents from the index, as well as dynamic whitelisted domains for image uploads and various bug fixes.
  • Additionally, the pagination issue on the order listing page is resolved with the correct page numbers now being displayed.
  • - Minor code refactoring for readability
  • - Improved query performance by adding storeId index to product attributes table
  • 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 bug where product attributes were not being filtered by store id
  • Fixed issue where product attributes were not properly filtered by store id
  • - Resolved issue to improve overall functionality and user experience
  • - Ensured store id is included in query to accurately retrieve product attributes for specific store
  • Database performance improvements through the addition of indexes to key tables and fields
  • Refactored code for better control flow and debugging capabilities in the Meilisearch indexing loop.
  • This also includes minor code refactoring and formatting updates.
  • Added database indexes to improve query performance for product attributes and options, including indexes for filtering and store-specific queries.
  • Improved query performance for product attributes and options tables through the addition of database indexes.
  • Refactored the refreshMeilisearchIndex function to use a do-while loop and added logging for debugging product fetching and ID tracking.
  • 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.
  • Added comprehensive image uploads management functionality, including a new service and UI page, and minor code updates for consistency and formatting.
  • - Close issue #456 (assuming related issue)
  • - Update documentation to reflect changes
  • - Revert related changes in other files
  • - Revert changes made to the meilisearch search route
  • - Revert changes made to meilisearch search route
  • - Fix bug with search route not returning results
  • - Fix bug causing incorrect search results
  • Resolved an issue with deleting Product entries through a sheet by fixing the deletion of associated ImageUpload entries.
  • Fixed a bug related to ImageUpload not being deleted when a product is deleted
  • Demonstrated attention to detail and thorough testing by identifying and fixing this specific issue.
  • Improved the overall functionality and user experience of deleting products through a sheet
  • Addressed an issue with deleting entries for products through a sheet
  • Improved the functionality of the system by ensuring that all associated data is properly deleted when a Product is deleted.
Version v8.37
September
Week 37 2025
  • Fixed Meilisearch filter strings for correct string matching.
  • - Added proper HTTP status codes to error responses in admin orders list endpoint
  • Fixed HTTP status codes in error responses for post-sale payment handlers and admin orders list endpoint.
  • - Fixed filter strings in Meilisearch to improve search accuracy and functionality.
  • - 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.
  • Development points:
  • 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
  • Fix for issue causing incorrect error messages when deleting addresses
  • Addressed an issue with deleting addresses that could cause confusion for users.
  • Enhanced user experience by providing a more informative error message.
  • Enhancement to address deletion feature for better user experience
  • Improved error message when deleting an address that violates a foreign key constraint.
  • Improved error messaging for address deletion violating foreign key constraint
  • Resolved error with creating a stripe session and finding currency table.
  • Fixed issue with listing customers in admin route.
  • Improved user interface by hiding admin not approved warning.
  • Improved user interface by hiding a warning for unapproved admin users and listing customers in the admin-customer route.
  • Fixed security issue by hiding sensitive information and resetting link in admin-forgot-password route.
  • Improved security by hiding sensitive information and resetting links from the admin-forgot-password route.
  • Addressed errors related to creating a stripe session and not finding the currency table.
  • route
  • -customer
  • Refactored server code for email verification page to improve readability.
  • 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.
  • 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.
  • - Updated notification history queries to use isAdmin flag for admin-specific notifications
  • - Removed storeId from token and userId validation logic in auth handlers
  • A fix has been made for typecasting errors with the order number.
  • The parent order number has been updated to use a sequence.
  • The order number is now an integer.
  • Litekart removed from login page to accommodate for white labeling.
  • White labeling feature introduced with `isWhiteLabeled` variable and removal of Guides on login page.
  • A fix has been made for a TypeScript error.
  • Guides have been removed for white labeled versions.
  • Fixed order number typecast and ts-error, and updated order_no to be an integer and parentorderno to be a sequence.
  • The store now has a new feature called `isWhiteLabeled`.
  • The `distinctAttribute` has been renamed to `distinct`.
  • The login page no longer includes Litekart.
Version v8.35
August
Week 35 2025
  • Implementation of customer_id instead of user_id for improved user identification and tracking.
  • 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 a new identifier system: The commits involve changing the user_id to customer_id, indicating the implementation of a new identifier system for customers.
  • The customer list has been separated from the user list.
  • Improved functionality and bug fixes related to shipping zones, formatting, and order detail loading.
  • 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.
  • Shipping zone creation now occurs after the store has been created.
  • Introduction of new features, such as admin activities and notification history, and updates to existing endpoints.
  • The meilisearch version has been reverted to 0.48.2.
  • The storeId has been fixed in the auth/signup process.
  • Admin activities have been introduced, including a new endpoint for admin user registration and a new feature for tracking notification history.
  • The create-order function has been separated and confirm-order has been moved to its own file.
  • Customer queries now require a storeId.
  • Implementation of new admin API routes for managing return reasons and updates to dependencies for improved performance.
  • Separation of customer list and user list for improved organization and management.
  • Improved customer query functionality with the addition of storeId and updates to order and confirmation processes.
  • Enhanced security by fixing password validation and implementing token validation checks in auth handlers.
  • Refactored schema relations to reference the AdminUser model instead of the Customer model, and replaced Customer references with AdminUser.
  • 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.
  • Added new API handlers for products, imports, carts, and settings routes, and created initial e-commerce API routes and database schema files.
  • Improved type safety and refactored customer schema and handlers for better organization and maintainability.
  • Updated Stripe API version and simplified database migration scripts, as well as updating TypeScript build and buildx scripts.
  • 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.
  • Refactored chat schema to use OpenAPI variants and updated return type checking in handlers.
  • Added various admin routes and handlers, as well as core API routes and handlers.
  • 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.
  • Implementation of various admin routes and handlers for background jobs, banners, auth, blogs, and more
  • Implemented order management and payment processing endpoints with multiple gateways.
  • Refactoring of chat schema references to use OpenAPI variants
  • 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.
  • 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.
  • The addition of API routes improves the overall functionality and usability of the system.
  • This development allows for easier access and manipulation of data within these modules.
  • 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.
Version v8.34
August
Week 34 2025
  • 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 initial development focused on creating API routes and handlers for various modules such as checkout, inventory, settings, and varni.
  • Core e-commerce functionality, including payments, shipping, and checkout, was implemented through additional API routes.
  • The team then added API routes for core e-commerce functionality, specifically payments, shipping, and checkout.
  • Finally, they implemented the initial database schema and API routes for overall e-commerce functionality.
  • Migration of hierarchical category slugs
  • Migration to hierarchical category slugs
  • Improved organization and structure of product and category URLs.
  • Implementation of store-scoped product slugs
  • Addition of new features to improve store functionality
  • Implemented multi-payment gateway integration with PayPal, PhonePe, Stripe, and Affirm.
  • Improved product caching and ordering by moving outside of conditional block and removing createdAt ordering.
  • Added payment handlers for Affirm, PayPal, and PhonePe checkout.
  • Added support for multiple payment gateways, including PayPal, PhonePe, Stripe, and Affirm.
  • Integrated Stripe payment with session management and webhooks.
  • Integrated Stripe payment system with session management and webhooks.
  • Implemented a queue system for image uploads during product imports.
  • Updated dependencies, including @antfu/eslint-config and @arcjet packages.
  • Implemented a queue system for uploading product images during imports.
  • Improved product caching and removed unnecessary ordering for better performance.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
Version v8.32
August
Week 32 2025
  • Increased efficiency by removing case-insensitive string comparisons in payment method lookups.
  • Improved readability by deconstructing parameters for Razorpay order creation.
  • , improved readability and removed case-insensitive comparisons
  • Improved readability of Razorpay order creation parameters by restructuring them.
  • Fixed payment method selection by code instead of name and added code field to response for more accurate matching.
  • Enhanced payment method selection by using code instead of name and adding a code field to the response.
  • Eliminated case-insensitive string comparisons in payment method lookups.