Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Major Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - With this version, the @refinedev/nextjs-router package now starts supporting Next.js@14 and App Router by default. You can upgrade your application by following the upgrade guide.

  We recommend that projects using Ant Design refrain from upgrading at the moment due to the incompatibility between Ant Design and Next.js 14 Pages Router. For more detailed information, you can refer to the Known Issues document in Ant Design here.

  Upgrade Guide

  npm i next@14 @refinedev/nextjs-router@latest
  

  See Next.js 14 Upgrade Guide and Next.js 14 Codemods for more information.

  Changes to default export

  Default export for @refinedev/nextjs-router is now App Router instead of Pages.

  If you are using Pages, update your imports as follows:

  - import routerProvider from "@refinedev/nextjs-router";
  + import routerProvider from "@refinedev/nextjs-router/pages";
  

  If you are using App Router, update your imports as follows:

  - import routerProvider from "@refinedev/nextjs-router/app";
  + import routerProvider from "@refinedev/nextjs-router";
  

  Changes to parseTableParams import

  If you will use parseTableParams on client side for App Router, you can use the following import:

  import { parseTableParams } from "@refinedev/nextjs-router";
  

  parseTableParams from @refinedev/nextjs-router has "use client" directive.

  If you want to use parseTableParams on server side for App Router, you can use the following import:

  import parseTableParams from "@refinedev/nextjs-router/parse-table-params";
  

  parseTableParams from @refinedev/nextjs-router/parse-table-params doesn't have "use client" directive.

  Dropped Refine v3 router provider legacy support

  Now, @refinedev/nextjs-router only supports Refine v4 router provider.

  The following exports are removed:

  - @refinedev/nextjs-router/legacy
  - @refinedev/nextjs-router/legacy-app
  - @refinedev/nextjs-router/legacy-pages
  

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

• Updated dependencies [546df06482]:

  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

• Updated dependencies [546df06482]:

  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Patch Changes

• Updated dependencies [546df06482]:
  • @refinedev/[email protected]

Patch Changes

• Updated dependencies [546df06482]:
  • @refinedev/[email protected]
  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

• Updated dependencies [546df06482]:

  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

• Updated dependencies [546df06482]:

  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

• Updated dependencies [546df06482]:

  • @refinedev/[email protected]
  • @refinedev/[email protected]
  • @refinedev/[email protected]

Patch Changes

• #5573 546df06482 Thanks @alicanerdurmaz! - fix: when antd imports destructed outside react component, gives undefined error on ESM build.

• #5573 546df06482 Thanks @alicanerdurmaz! - chore: add "use client" directive to exported files to work with nextjs app router

Patch Changes

• Updated dependencies []:
  • @refinedev/[email protected]

Patch Changes

• #5597 1738981da0 Thanks @alicanerdurmaz! - fix: meta has corrupted route parameters.

  parse function from @refinedev/nextjs-router provides returns search params as following structure:

  {
      "pageSize": "25",
      "current": "1",
      "sorters[0][field]": "status",
      "sorters[0][order]": "asc",
      "filters[0][field]": "status",
      "filters[0][value]": "draft",
      "filters[0][operator]": "contains"
  }
  

  This structure is not predictable and not sanitazble. So, parse function has been updated to provide following structure:

  {
      "pageSize": "25",
      "current": "1",
      "sorters": [
          {
              "field": "status",
              "order": "asc"
          }
      ],
      "filters": [
          {
              "field": "status",
              "value": "draft",
              "operator": "contains"
          }
      ]
  }
  

  With this schema we can easily sanitize, deduplicate and predict the structure of the query parameters.

Patch Changes

• #5592 b10a66b58d Thanks @BatuhanW! - fix: add graphql package as dependency.

  New projects created with create refine-app is failing to start due to missing graphql package.

Patch Changes

• #5568 f1244819ad Thanks @alicanerdurmaz! - feat: notificationProvider is deprecated due to consistent naming convention between UI libraries. Please use useNotificationProvider export as your notification provider. #5567

• #5564 1bb7d30888 Thanks @alicanerdurmaz! - feat: <ThemedTitleV2 />'s default icon updated.

Patch Changes

• #5552 8c50a6bd83 Thanks @alicanerdurmaz! - feat: added meta.schema parameter to supabase dataprovider. #5551

  From now on, users will be able to specify the schema for queries using data hooks, allowing them to override the default schema in the supabase client.

  const tableProps = useTable<IUser>({
      resource: "posts",
      meta: {
          schema: "foo",
      },
  });
  

Patch Changes

• #5576 096336a33a Thanks @billy-wong-tech! - fix(strapi-v4): pass meta.publicationState query params to getOne method.

Patch Changes

• #5378 63e39ed312 Thanks @amanzrx4! - fix: dataProvider.getList method adds ? to the request url when there is no filters, sorters and pagination in the request. #5359

  - Expected
  + Received
  
  - "https://api.fake-rest.refine.dev/categories",
  + "https://api.fake-rest.refine.dev/categories?",
  

  From now on, dataProvider.getList method will not add ? to the request url when there is no filters, sorters and pagination in the request.