Guides
Removing Internationalization
Learn how to remove internationalization from your Nextbase application
Many saas products require internalization. But many don't need it too. Ultimately it is your customer requirements that matter.
If you don't need internationalization, you can remove it by following these steps:
- Move all the children of the
src/app/[locale]
folder to thesrc/app/
folder. - Remove the
[locale]
from thesrc/app/
folder. - Remove the
next-intl
from thepackage.json
file. - Update your middleware to this pattern. Pay close attention to the
- Remove
src/i18n
folder. - Replace all
import { Link } from "@/components/intl-link";
withimport Link from "next/link";
- Remove all
LocaleSwitcherSelect
component and its usage - Remove
import createNextIntlPlugin from "next-intl/plugin"
and its usage innext.config.mjs
- Remove
unstable_setRequestLocale
usage in all static pages andlocale
from 'params'. - Remove
useTranslations
usage in all client components. - Remove
getMessages
usage in root layout component and removelocale
andmessages
props fromAppProviders
component. Finally removeNextIntlProvider
from theAppProviders
component.
Optimizing Data Operations in Next.js 14 and Supabase
Learn how to efficiently fetch and mutate data in Next.js 14 and Supabase using server components, useToastMutation, and Supabase real-time APIs.
Row Level Security
Row Level Security in NextBase is a powerful feature that allows you to control access to rows in your database based on the user who is querying the data.