Mantine Vite template

One ⭐ is the best and the easiest support you can give. <3

This template comes with the following features:

• PostCSS with mantine-postcss-preset
• TypeScript
• Redux-toolkit with redux-persist
• Storybook
• Vitest setup with React Testing Library
• ESLint setup with eslint-config-mantine
• Internationalization using i18next
• Custom auth hooks
• App configuration
• Yup schema validation
• Axios setup
• React Router Setup

Install deps and run the development server:

yarn && yarn dev

Open http://localhost:5111 with your browser to see the result.

• dev – start development server
• build – build production version of the app
• preview – locally preview production build

• typecheck – checks TypeScript types
• lint – runs ESLint
• prettier – checks files with Prettier
• vitest – runs vitest tests
• vitest:watch – starts vitest watch
• test – runs vitest, prettier, lint and typecheck scripts

• storybook – starts storybook dev server
• storybook:build – build production storybook bundle to storybook-static
• prettier:write – formats all files with Prettier

This template was created for users who want production level template but also do not want to spend to much time on configuring some stuff like authentication or axios. The template also supports multiple layouts that are available in mantine ui. For more information and details on how you can make changes in the template and configure it for your needs please check out the wiki.

You can check the wiki's for more detailed documentation on how to get the best out of this template -> Wiki's-link.

Any contribution is welcomed :).

The mock API runs only in development when enableMock is true. Demo credentials are prefilled on the sign-in page. Production uses the real API at apiPrefix; configure it before deploying.

Sign-in expects an access_token and user profile with an authority array. An optional expires_in value (seconds) enables automatic session expiry. Token refresh is not implemented; expired sessions require signing in again. Sessions persist in localStorage, so backend authorization is required for every protected operation. An HttpOnly cookie session requires backend support and a corresponding client integration.