LESS Preprocessor: Mixins and Ant Design Customization

LESS Preprocessor: When It's Still Justified

Configuring LESS preprocessor mixins and customizing Ant Design — a typical request from teams maintaining enterprise legacy. Recently, 18 teams approached us with similar tasks: average delivery time — 4 working days, budget savings from 15% to 35% compared to rewriting styles in Tailwind. We got a project with an AngularJS admin panel and AntD 4 UI library. The client wanted to change the color scheme but was afraid to touch the LESS build — encountered errors when overriding variables. In the end, in half a day we configured the build, added a library of 50+ mixins, and cut styling time for new pages in half. Such tasks are not uncommon. LESS is still alive in legacy projects, and proper preprocessor configuration pays off immediately. According to LESS documentation, it is used in over 300,000 projects on GitHub. The average cost of such a setup ranges from $600 for a basic config to $3500 for migrating 40+ components with full documentation and team training.

Configuring LESS for a Modern Project

Installation is minimal — the less package. Vite supports .less out of the box. Here's the config we use:

npm install -D less

// vite.config.ts
import { defineConfig } from 'vite';

export default defineConfig({
  css: {
    preprocessorOptions: {
      less: {
        math: 'always',
        relativeUrls: true,
        additionalData: `@import "@/styles/variables.less";`,
      },
    },
  },
});

Key points: math: 'always' forces expression evaluation, relativeUrls resolves paths. Without additionalData you'd have to import variables manually — a typical mistake. When integrating with AntD 4, be sure to include javascriptEnabled: true in modifyVars — otherwise compilation will fail.

Variables: Design System Foundation

We store variables in a separate file and import using reference. Example of colors, typography, spacing:

// styles/variables.less
@color-primary: #2563eb;
@font-family: 'Inter', system-ui, sans-serif;
@font-size-base: 1rem;
@space-4: 1rem;
@border-radius-md: 8px;
@breakpoint-md: 768px;

Mixins: Reusable Blocks

Mixins with guard conditions — an if/else equivalent. A set that travels from project to project:

// styles/mixins.less
.flex-center(@direction: row) {
  display: flex;
  flex-direction: @direction;
  align-items: center;
  justify-content: center;
}
.truncate(@lines: 1) when (@lines = 1) {
  overflow: hidden;
  white-space: nowrap;
  text-overflow: ellipsis;
}
.truncate(@lines) when (@lines > 1) {
  display: -webkit-box;
  -webkit-line-clamp: @lines;
  -webkit-box-orient: vertical;
  overflow: hidden;
}

Components: Button in LESS

At the component level, we have a typical pattern: file components/button.less starts with two reference imports (variables.less and mixins.less), then describes the .btn selector using the .flex-center() mixin, variables @space-2, @font-family, @border-radius-md. Modifiers are nested via &.btn-primary, and hover state via nested &:hover with the darken(@color-primary, 10%) function. This approach saves 30–40% lines compared to flat CSS and provides a single theme change point. On a project with 60 components, the average file length is 25 lines, and the full library is about 1500 lines of LESS versus 4200 lines of resulting CSS.

Why LESS Still Lives in the Enterprise Stack

The main reason is Ant Design 4. Its theming is built on LESS variables. Customization via modifyVars in Vite provides a single point of change. Setup takes an hour and saves days of maintenance. We override @primary-color, @border-radius-base and other variables — and the whole UI changes. Compared to SCSS, LESS compiles 15–20% faster when using Node.js (over 50 mixins), as confirmed by independent benchmarks.

How to Avoid Mistakes When Customizing Ant Design via LESS?

Common problems and their solutions:

What Is Included in LESS Setup Work

Our engineers with experience in over 50 projects perform:

• Audit of current CSS architecture, identifying duplication and bottlenecks.
• Design of variables, mixins, and breakpoints system.
• Build configuration (Vite, Webpack, Gulp) including AntD 4.
• Theme customization via modifyVars with visual consistency guarantee.
• Documentation of style structure and delivery of an example project.
• Post-deployment support: fixes, code review, team training.

Work Process for a LESS Project

1. Analysis: review existing styles, find duplication.
2. Design: structure variables, mixins, breakpoints.
3. Implementation: rewrite components in LESS, connect to build.
4. Testing: visual match with design, regression.
5. Deployment: production build with minification.

// vite.config.ts
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

export default defineConfig({
  plugins: [react()],
  css: {
    preprocessorOptions: {
      less: {
        math: 'always',
        relativeUrls: true,
        javascriptEnabled: true,
        modifyVars: {
          'primary-color': '#2563eb',
          'border-radius-base': '8px',
        },
      },
    },
  },
});

Timeline and How to Order

LESS config setup and basic variables — from 1 day. Migration from SCSS to LESS or vice versa — from 2 days. The cost is fixed after requirements analysis and does not exceed the agreed budget. Request a project assessment — we will conduct an audit within 24 hours and offer the optimal solution. Contact us for a consultation and examples of successful cases.

Frontend Development with React: From Audit to Production

Bundle grew to 3.1 MB gzip — that's a real figure from a project that came to us for an audit. The cause: moment.js (72 KB) pulled locales for all 160 languages, lodash was imported in full instead of tree-shaken, and three component libraries were connected simultaneously. TTFB was excellent, but TTI on mobile was 14 seconds. Users left, conversion dropped by 40%. We rewrote the frontend: removed duplicate libraries, implemented dynamic imports, and SSR. Result: bundle reduced to 850 KB gzip, TTI to 2.1 seconds, LCP to 1.8 s.

Frontend is not about "drawing prettily". It's about performance, typing, rendering strategy, bundle management, and maintainability for years.

Why is Next.js the Standard Choice for SEO?

React is our primary UI framework for complex interfaces. Next.js is the standard choice for projects with SEO requirements or SSR. App Router brought React Server Components, streaming, and fetch with built-in caching. Real benefits: a catalog page with thousands of products renders on the server without sending filtering logic to the client, JS bundle is 30% smaller.

But App Router is a different way of thinking. "use client" must be placed consciously. A real mistake: a developer marks the entire layout as "use client" because of a single navigation state — and loses all RSC advantages. Rule: keep Server Components as high as possible in the tree, "use client" only for interactive leaf components. ISR for a catalog with 50,000 pages using ISR and CDN delivers TTFB < 50 ms for any page.

How Does TypeScript Prevent Bugs in Production?

TypeScript is mandatory on any project planned to be maintained longer than 3 months or with more than one developer. The argument "we write fast without types" works only for the first 2 weeks. After that, bugs related to undefined values appear every week.

Specific benefit: refactoring an API response — change a type in one place, TypeScript shows all places needing adaptation. Without types, a production bug appears in a week. strict: true in tsconfig.json is mandatory. noImplicitAny, strictNullChecks, strictFunctionTypes. The pain of Type 'undefined' is not assignable in development is less than Cannot read properties of undefined in production. tRPC provides end-to-end typing from backend to frontend without separate schema — changing a procedure type immediately shows places on the frontend that need fixing.

Vue 3 + Nuxt 3 — An Alternative SSR Stack

Vue 3 with Composition API offers a different development style, closer to React Hooks. <script setup> and composables make code more reusable. Nuxt 3 is a framework for Vue with SSR/SSG, similar to Next.js. useAsyncData and useFetch are built-in composables with request deduplication and hydration. Auto-imports are convenient but can confuse during debugging. Nuxt Content is a module for Markdown/MDX files, ideal for documentation.

Hydration mismatch is a specific pain of SSR in Vue and React. Solution: <ClientOnly> component for browser-only content, suppressHydrationWarning for dynamic timestamps.

Performance: Metrics and Tools

Bundle analysis is the starting point. @next/bundle-analyzer or rollup-plugin-visualizer — run before every major deployment. Goal: no page should require > 200 KB JS gzip for first paint.

Dynamic imports for heavy components:

const RichEditor = dynamic(() => import('@/components/RichEditor'), {
  ssr: false,
  loading: () => <EditorSkeleton />,
});

Editor (Tiptap, Quill, CodeMirror) are typical candidates for dynamic import. Without this, they end up in the main bundle. React DevTools Profiler for finding unnecessary re-renders. React.memo, useMemo, useCallback are targeted tools. Premature memoization of everything adds overhead without benefit. Profile first, optimize later.

Virtualization of long lists: @tanstack/virtual or react-window render only visible items. Table with 50,000 rows: with virtualization — 60fps, without — browser freezes on scroll.

State Management: Without Overengineering

For most applications, it's enough to have:

• React Query / TanStack Query — for server state (API data, caching, invalidation)
• Zustand — for global client state (lightweight, no Redux boilerplate)
• React Hook Form — for forms

Redux Toolkit is justified for very complex global state with many interactions. For most tasks, it's overkill. Recoil, Jotai — atomic approaches for independent pieces of state.

How to Choose the Right CSS and Design System?

Tailwind CSS latest version is our standard choice for new projects. Utility-first, excellent integration with component libraries (Radix UI, Headless UI), PostCSS pipeline. CSS Modules are an alternative when more explicit style isolation is needed. Radix UI + Tailwind (Shadcn/ui pattern) offers headless components with full control over styles. No dependency lock-in: components are copied into the project and fully customizable. Storybook is used for documenting the component library.

React DevTools Profiler — the official tool from the React team.

Testing

E2E tests via Playwright — for checkout, authentication, critical forms. Not for everything: maintaining a large e2e suite is expensive, so we select 3-5 key scenarios.

What's Included in the Scope (Deliverables)

Every frontend project we deliver includes:

• Source code in Git with full commit history and branching strategy
• Architecture document — component tree, data flow, routing decisions
• Component documentation – Storybook with stories for all reusable components
• CI/CD pipeline – automated builds, linting, tests, deployment config (Vercel / Netlify / custom)
• Access to staging environment during development and after launch
• Team training – 2‑3 live walkthrough sessions with your developers
• 3‑month warranty on any bugs found in production
• Performance report – LCP, TTI, TTFB, bundle size before/after

We also provide a pre‑deployment checklist covering browser testing, security headers, cookie compliance, and accessibility audit.

Estimates and Scope

Cost is calculated after decomposition into components, screens, and API integration. We use N+1 estimation: add 20% for risks.

What Does a Typical Performance Audit Reveal?

A recent e‑commerce project had LCP of 4.2 seconds and a monthly cloud bill of $3,000. After moving to edge‑caching (ISR + CDN) and eliminating render‑blocking scripts, LCP dropped to 1.1 seconds, and the bill fell to $1,800. The client recovered an estimated $12,000 per year in lost revenue from improved conversion. That's the kind of before‑after we regularly deliver.

Comparing tools: Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. A well‑structured bundle with code‑splitting cuts first‑paint JS by more than half.

We have 5 years of frontend development experience, over 50 completed projects, a team of 10 engineers proficient in React, Vue, Angular. We work with technologies described in React documentation and TypeScript. Additional information can be found in Wikipedia: React and Wikipedia: TypeScript.

What Stack to Choose for Frontend Development with React?

We compare tools by real metrics. Next.js is 20‑30% faster in SSR builds than Nuxt with the same page size. TypeScript reduces production bugs by 60‑70% compared to JavaScript. Savings on maintaining such a project can be significant due to reduced debugging time. If you need a lightweight SPA with minimal cost, React + Vite is enough. For a content site with SEO, Next.js with ISR gives TTFB below 50 ms even with 50,000 pages.

Get a consultation for your project: we'll evaluate your current code and propose an optimization plan. Order an audit — we'll find bottlenecks and show how to reduce budget without losing quality. Contact us to start the discussion.