Files

Giancarlo Buomprisco 5b9285a575 Next.js 15 Update (#26 )

* Update Next.js and React versions in all packages
* Replace onRedirect function with next/link in BillingSessionStatus, since it's no longer cached by default
* Remove unused revalidatePath import in billing return page, since it's no longer cached by default
* Add Turbopack module aliases to improve development server speed
* Converted new Dynamic APIs to be Promise-based
* Adjust mobile layout
* Use ENABLE_REACT_COMPILER to enable the React Compiler in Next.js 15
* Report Errors using the new onRequestError hook

2024-10-22 14:39:21 +08:00

src

Next.js 15 Update (#26 )

2024-10-22 14:39:21 +08:00

package.json

Next.js 15 Update (#26 )

2024-10-22 14:39:21 +08:00

README.md

Refactor billing code and add error monitoring

2024-04-25 13:19:46 +07:00

tsconfig.json

Refactor billing imports, reorganize package scripts and improve action structure

2024-04-07 12:47:29 +08:00

README.md

Next.js Utilities / @kit/next

This package provides utilities for working with Next.js.

Server Actions

The enhanceAction function allows you to wrap a Next.js Server Action with additional functionality.

import { enhanceAction } from '@kit/next/actions';

export const myServerAction = enhanceAction(async (data, user) => {
  // "data" has been parsed with the schema
  // and will correctly be typed as the schema type
  // in the case below, data will be of type { id: number }
  
  // "user" is the user object from the session
  
  // if "captcha" is true, the action will require a captcha
}, {
  captcha: true,
  schema: z.object({
    id: z.number()
  }),
});

The enhanceAction function takes two arguments:

The action function
An options object

The options object can contain the following properties:

captcha - If true, the action will require a captcha to be passed to the body as captchaToken
schema - A zod schema that the data will be validated against
captureException - If true, the action will capture exceptions and report them to the configured provider. It is true by default.

When successfully called, the action will return the result of the action function.

The user will be automatically authenticated and the result will be passed as the second argument to the action function.
The data will be parsed/validated with the schema and passed as the first argument to the action function.
If the captcha option is true, the action will require a captchaToken to be passed in the body.

The consumer can call the action like so:

import { myServerAction } from 'path/to/myServerAction';

const result = await myServerAction({ id: 1 });

or with an optional captcha token:

import { myServerAction } from 'path/to/myServerAction';

const result = await myServerAction({ id: 1, captchaToken: 'captchaToken' });

Route Handlers

The function enhanceRouteHandler allows you to wrap a Next.js API Route Handler with additional functionality.

import { enhanceRouteHandler } from '@kit/next/routes';

export const POST = enhanceRouteHandler(({ request, body, user }) => {
  // "body" has been parsed with the schema
  // and will correctly be typed as the schema type
  // in the case below, data will be of type { id: number }

  // "user" is the user object from the session
  
  // "request" is the raw request object passed by POST
  // if "captcha" is true, the action will require a captcha
  // if "captureException" is true, the action will capture exceptions and report them to the configured provider
}, {
  captcha: true,
  captureException: true,
  schema: z.object({
    id: z.number()
  }),
});

When using a Captcha, the consumer will pass an header x-captcha-token with the captcha token.