LowFile-scopeJavaScript / TypeScript Plug & play

Dynamic import for heavy client-only widgets

Use next/dynamic with { ssr: false } for large client-only components (maps, editors) and provide a lightweight loading fallback.

Add to Mesrai Open workspace

Why this matters

Avoids SSR cost and reduces JS sent to the client.

Bad vs. good

Side-by-side examples engineers can pattern-match during review.

Avoid

import Map from './map'
export default function Page(){ return <Map /> }

Prefer

import dynamic from 'next/dynamic'
const Map = dynamic(()=>import('./map'),{ ssr:false, loading:()=> <div>Loading map…</div> })
export default function Page(){ return <Map /> }

More snippets

Bad

Static import of a heavy editor

Good

dynamic(...,{ ssr:false })

Related rules

From the same buckets as this rule.

High
Keep 'use client' at the leaf: default to Server Components
Prefer Server Components for pages/layouts and move interactivity to small leaf Client Components. Only add 'use client' where browser APIs or event handlers are strictly necessary.
stack-nextjsstack-react+2
High
Make fetch caching explicit in Server Components
For dynamic data use { cache: 'no-store' } or file-level dynamic = 'force-dynamic'. For ISR use { next: { revalidate: N, tags: [...] } }.
stack-nextjsstack-react+2
High
Middleware only for light auth/rewrites
Keep middleware fast and side-effect free (no DB writes). Narrow the matcher and skip static assets. Use Route Handlers for heavy logic.
stack-nextjsstack-react+2

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites

Why this matters

Bad vs. good

More snippets

Related rules

Keep 'use client' at the leaf: default to Server Components

Make fetch caching explicit in Server Components

Middleware only for light auth/rewrites