v7.9.6

7.9.6 (2024-10-22)

Bug Fixes

• validation-errors: type inference for branded, nullable, optional and array types (#284) (2e1fe62)

v7.9.5

7.9.5 (2024-10-21)

Refactors

• clean up some logic (f8519cc)

v7.9.4

7.9.4 (2024-10-12)

Refactors

• hooks: deprecate executeOnMount (45e0f96)

v7.9.3

7.9.3 (2024-09-13)

Bug Fixes

• export SafeActionClient type to make it portable (#267) (#269) (197ec51), closes #64

v7.9.3-beta.1

7.9.3-beta.1 (2024-09-13)

Bug Fixes

• export SafeActionClient type to make it portable (#267) (d2d7bdd), closes /typescript.tv/errors/#ts2742

v7.9.2

7.9.2 (2024-09-08)

Refactors

• pass utils to validation errors shape customizer functions (#263) (a789d0a), closes #256

v7.9.1

7.9.1 (2024-09-08)

Refactors

• remove additional fetchError prop from hook return object (#262) (3d32f9d)

v7.9.1-beta.1

7.9.1-beta.1 (2024-09-07)

Refactors

• remove additional fetchError prop from hook return object (d8a3352)

v7.9.0

7.9.0 (2024-09-04)

Features

• merge server error handling functions into handleServerError (#257) (c900720)

Description

v7.9.0 merges the functionality of handleServerErrorLog and handleReturnedServerError functions into a single optional initialization function called handleServerError. This change has been made because having two functions for server error handling is unnecessary, you can easily manage both logging and returned error within a single function.

Upgrade guide

Suppose you have this code using next-safe-action < 7.9.0:

import { createSafeActionClient } from "next-safe-action";

const actionClient = createSafeActionClient({
  // handles logging
  handleServerErrorLog(error) {
    console.error("my custom error log:", error.message);
  },
  // handles returned shape
  handleReturnedServerError(error) {
    return {
      message: error.message,
    };
  },
});

With next-safe-action >= 7.9.0 it becomes:

import { createSafeActionClient } from "next-safe-action";

const ac = createSafeActionClient({
  // handles both logging and returned shape
  handleServerError(error) {
    console.error("my custom error log:", error.message);
    return {
      message: error.message,
    };
  },
});

So, minimal refactoring is required, and the action client creation is cleaner this way.

---

Note

Even if you want to change just the logging mechanism, you still have to return an error shape from handleServerError, otherwise the resulting type would be void.

So, if you want for instance keep the default error message as the returned server error and just update the console logging, you can do it like this:

import { createSafeActionClient, DEFAULT_SERVER_ERROR_MESSAGE } from "next-safe-action";

const ac = createSafeActionClient({
  handleServerError(error) {
    console.error("my custom error log:", error.message);
    return DEFAULT_SERVER_ERROR_MESSAGE;
  },
});

v7.8.2

7.8.2 (2024-09-02)

Documentation

• update library description (8e654bc)