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 getChaiBuilderTailwindConfig export (a v3 tailwind.config.js helper) and the tailwindCSS editor prop are removed. @tailwindcss/container-queries is 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 bare ring and outline-none used 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/render RenderChaiBlocks ChaiBlocksRenderer
    ChaiPageCSS, ChaiPageJSONLD, PageScripts ChaiPageCss, ChaiPageJsonLd, ChaiPageScripts
    WithChaiLayout ChaiLayout
    getStylesForBlocks, getMergedPartialBlocks getChaiBlocksStyles, getChaiMergedPartialBlocks
    chaipro/nextjs/render-client PreviewBanner ChaiPreviewBanner
    chaipro/nextjs/server ActionError ChaiActionError
    db, schema, getDb, safeQuery chaiDb, chaiSchema, getChaiDb, tryChaiDbQuery
    dispatchChaiAction runChaiAction
    hasPermission, resolvePermissions, getPermissionCatalog hasChaiPermission, resolveChaiPermissions, getChaiPermissionCatalog
    withActionPermission, mergeDefaultRoleGrants withChaiActionPermission, mergeChaiDefaultRoleGrants
    ChaiActionsRegistry, BuilderActionsRegistry chaiActionsRegistry
    chaipro useFetch, useBuilderFetch, useApiUrl useChaiActionFetch, useChaiApiUrl
    useActivePage, useWebsitePages, useWebsiteSetting useChaiActivePage, useChaiPrimaryPages, useChaiSiteSettings
    useSavePage, usePageTypes, useSiteGlobalData useChaiSavePage, useChaiPageTypes, useChaiSiteGlobalData
    useUserPermissions, useTranslation useChaiUserPermissions, useChaiTranslation
    PermissionChecker, ImagePicker, LanguageSwitcher IfChaiPermission, ChaiImagePicker, ChaiLanguageSwitcher
    registerChaiPreImportHTMLHook registerChaiPreImportHtmlHook
    chaipro/registry getAllRegisteredChaiBlocks, getAllRegisteredFonts getRegisteredChaiBlocks, getRegisteredChaiFonts
    setChaiBlockComponent registerChaiBlockComponent
    getFontStyles, getRegisteredFont, useRegisteredFonts getChaiFontStyles, getRegisteredChaiFont, useRegisteredChaiFonts
    chaipro/utils applyDesignTokens, getChaiBuilderTheme applyChaiDesignTokens, getChaiTailwindTheme
    convertHTMLToChaiBlocks parseChaiBlocksFromHtml
    chaipro/payload createPayloadChaiBuilder createChaiPayloadBuilder
    buildChaiBuilderConfig buildChaiPayloadConfig
    chaipro/payload/builder ChaiWebsiteBuilder ChaiPayloadWebsiteBuilder
    chaipro/db/* createPostgresDB, createNodePgDB, createLibsqlDB, createD1DB createPostgresDb, createNodePgDb, createLibsqlDb, createD1Db
    chaipro/ai/openai-compatible openAICompatiblePlugin openAiCompatiblePlugin
    chaipro/plugins/* aiPlugin, aiProPlugin, aiProClientPlugin aiAdvancedPlugin, aiAdvancedClientPlugin

    ChaiWebsiteBuilder from chaipro and buildChaiBuilderConfig from chaipro/nextjs/server keep 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/server and /client; chaipro/plugins/ai-pro/* still works.

  • actions wins over builderActions. The deprecated builderActions key used to be merged last, so on a name clash it won. It is now merged first, so actions wins. On Payload, the order is Payload's defaults, then builderActions, then actions.

  • Export Code emits a Tailwind v4 CSS entry (@theme) instead of a tailwind.config.js object.

Added

  • withChaiActionPermission and mergeChaiDefaultRoleGrants are exported from chaipro/nextjs/server for plugin authors. See Plugins.
  • registerChaiClientPlugin registers one client plugin from a setup file.
  • New subpaths: chaipro/plugins/ai-advanced/server and /client, chaipro/plugins/bulk-publish/client, chaipro/plugins/empty-page-starter/client, chaipro/plugins/export-code/client, chaipro/db/schema-pg and chaipro/db/relations-pg.

Upgrade notes

  1. Upgrade the package with pnpm up chaipro@^0.5.2. No database migration is needed.
  2. Still on Tailwind v3? Move your app to Tailwind v4 first: remove the getChaiBuilderTailwindConfig config and the tailwindCSS editor prop, and install @tailwindcss/postcss.
  3. Check pages that use shadow-sm, drop-shadow-sm, blur-sm, backdrop-blur-sm, a bare ring or outline-none. They now look the way Tailwind v4 draws them.
  4. Pass the same action under both actions and builderActions? The actions one now wins. Move everything to actions.
  5. Rename at your own pace. Deprecated names keep working. Your editor strikes them through and names the replacement.

© ChaiBuilder. All rights reserved.

ChaiBuilderMade withChaiBuilder