* chore: update package versions and dependencies across multiple files - Bumped application version to 2.21.3 in package.json. - Updated dependencies including turbo to version 2.6.1, @next/bundle-analyzer and @next/eslint-plugin-next to version 16.0.3, and @supabase/supabase-js to version 2.81.1. - Adjusted @types/node, @types/react, and @types/react-dom versions for consistency. - Refactored package.json files to utilize catalog dependencies for improved management. - Incremented various other dependencies such as react-i18next to version 16.3.3 and tailwind-merge to version 3.4.0. * chore: downgrade @next/bundle-analyzer and @next/eslint-plugin-next to version 16.0.2 and update next to version 16.0.2 in pnpm-lock.yaml and pnpm-workspace.yaml - Updated package versions for consistency across the project. - Adjusted the overflow property in the PageWithSidebar component for improved layout handling. * feat: add sorting functionality to DataTable header - Implemented click handler for sortable headers in the DataTable component, allowing users to toggle sorting between ascending and descending order. - Enhanced user interaction by updating the header's visual state based on the current sorting direction. * fix: update layout and structure in UserHomePage and DashboardDemo components - Added a new div structure within the PageBody of UserHomePage for improved layout. - Simplified the grid structure in DashboardDemo by adjusting the number of columns for better responsiveness. - Enhanced the PageWithSidebar component to ensure proper flex behavior and layout consistency. * refactor: simplify PageBody structure in UserHomePage - Removed unnecessary div elements within the PageBody of UserHomePage for cleaner layout. - Enhanced readability and maintainability of the component structure.
Dev Tool
This is a Next.js project bootstrapped with create-next-app.
The Dev Tools is an application that helps you manage your Makerkit environment variables and other settings.
Getting Started
First, run the development server:
pnpm run --filter dev-tool dev
Open the link printed in the terminal to see the result.
Testing production environment variables
To test your production environment variables, create a .env.production.local file in the apps/web directory and add your production environment variables.
This environment variables are not committed to the repository, so you can use them for testing purposes.
In the environment mode switcher, please select Production to test your production environment variables.
Don't publish this app
This app is not intended to be published to the public. This is only meant to be used by for development purposes.