chaipro v0.5.2
Released 2026-11-17. Upgrading from v0.5.1.
Two things in this release. Tailwind CSS v3 support is gone. And the public API now follows one naming convention: about 190 exports have a new name, and every old name still works from the same import path, marked deprecated. Your code keeps compiling; your editor shows the new name.
Breaking
- Tailwind CSS v4 only. The
getChaiBuilderTailwindConfigexport (a v3tailwind.config.jshelper) and thetailwindCSSeditor prop are removed.@tailwindcss/container-queriesis no longer a dependency, since container queries are built into v4. See Theming. - Six classes render with Tailwind v4 values.
shadow-sm,drop-shadow-sm,blur-sm,backdrop-blur-sm, a bareringandoutline-noneused to be kept at their v3 values. They now compile to v4's own values, on the live page and in the canvas. Stored page styles recompile on the first request after the upgrade.
Changed
One naming convention. Hooks, components, functions and types carry
Chai, acronyms are written as words (Css,Html,JsonLd,Db,Ai), and each verb has one meaning (register*,get*,run*,create*,parse*). The old names stay exported, so nothing breaks. The most used renames:Import path Old name New name chaipro/nextjs/renderRenderChaiBlocksChaiBlocksRendererChaiPageCSS,ChaiPageJSONLD,PageScriptsChaiPageCss,ChaiPageJsonLd,ChaiPageScriptsWithChaiLayoutChaiLayoutgetStylesForBlocks,getMergedPartialBlocksgetChaiBlocksStyles,getChaiMergedPartialBlockschaipro/nextjs/render-clientPreviewBannerChaiPreviewBannerchaipro/nextjs/serverActionErrorChaiActionErrordb,schema,getDb,safeQuerychaiDb,chaiSchema,getChaiDb,tryChaiDbQuerydispatchChaiActionrunChaiActionhasPermission,resolvePermissions,getPermissionCataloghasChaiPermission,resolveChaiPermissions,getChaiPermissionCatalogwithActionPermission,mergeDefaultRoleGrantswithChaiActionPermission,mergeChaiDefaultRoleGrantsChaiActionsRegistry,BuilderActionsRegistrychaiActionsRegistrychaiprouseFetch,useBuilderFetch,useApiUrluseChaiActionFetch,useChaiApiUrluseActivePage,useWebsitePages,useWebsiteSettinguseChaiActivePage,useChaiPrimaryPages,useChaiSiteSettingsuseSavePage,usePageTypes,useSiteGlobalDatauseChaiSavePage,useChaiPageTypes,useChaiSiteGlobalDatauseUserPermissions,useTranslationuseChaiUserPermissions,useChaiTranslationPermissionChecker,ImagePicker,LanguageSwitcherIfChaiPermission,ChaiImagePicker,ChaiLanguageSwitcherregisterChaiPreImportHTMLHookregisterChaiPreImportHtmlHookchaipro/registrygetAllRegisteredChaiBlocks,getAllRegisteredFontsgetRegisteredChaiBlocks,getRegisteredChaiFontssetChaiBlockComponentregisterChaiBlockComponentgetFontStyles,getRegisteredFont,useRegisteredFontsgetChaiFontStyles,getRegisteredChaiFont,useRegisteredChaiFontschaipro/utilsapplyDesignTokens,getChaiBuilderThemeapplyChaiDesignTokens,getChaiTailwindThemeconvertHTMLToChaiBlocksparseChaiBlocksFromHtmlchaipro/payloadcreatePayloadChaiBuildercreateChaiPayloadBuilderbuildChaiBuilderConfigbuildChaiPayloadConfigchaipro/payload/builderChaiWebsiteBuilderChaiPayloadWebsiteBuilderchaipro/db/*createPostgresDB,createNodePgDB,createLibsqlDB,createD1DBcreatePostgresDb,createNodePgDb,createLibsqlDb,createD1Dbchaipro/ai/openai-compatibleopenAICompatiblePluginopenAiCompatiblePluginchaipro/plugins/*aiPlugin,aiProPlugin,aiProClientPluginaiAdvancedPlugin,aiAdvancedClientPluginChaiWebsiteBuilderfromchaiproandbuildChaiBuilderConfigfromchaipro/nextjs/serverkeep their names; only the Payload variants were renamed, because the same name meant two different things. The AI plugin also has new import paths,chaipro/plugins/ai-advanced/serverand/client;chaipro/plugins/ai-pro/*still works.actionswins overbuilderActions. The deprecatedbuilderActionskey used to be merged last, so on a name clash it won. It is now merged first, soactionswins. On Payload, the order is Payload's defaults, thenbuilderActions, thenactions.Export Code emits a Tailwind v4 CSS entry (
@theme) instead of atailwind.config.jsobject.
Added
withChaiActionPermissionandmergeChaiDefaultRoleGrantsare exported fromchaipro/nextjs/serverfor plugin authors. See Plugins.registerChaiClientPluginregisters one client plugin from a setup file.- New subpaths:
chaipro/plugins/ai-advanced/serverand/client,chaipro/plugins/bulk-publish/client,chaipro/plugins/empty-page-starter/client,chaipro/plugins/export-code/client,chaipro/db/schema-pgandchaipro/db/relations-pg.
Upgrade notes
- Upgrade the package with
pnpm up chaipro@^0.5.2. No database migration is needed. - Still on Tailwind v3? Move your app to Tailwind v4 first: remove the
getChaiBuilderTailwindConfigconfig and thetailwindCSSeditor prop, and install@tailwindcss/postcss. - Check pages that use
shadow-sm,drop-shadow-sm,blur-sm,backdrop-blur-sm, a bareringoroutline-none. They now look the way Tailwind v4 draws them. - Pass the same action under both
actionsandbuilderActions? Theactionsone now wins. Move everything toactions. - Rename at your own pace. Deprecated names keep working. Your editor strikes them through and names the replacement.
Related
- API Reference - the naming convention.
- chaipro v0.5.1 - the previous release.
- chaipro Changelog - all releases.

