A "use server" file can only export async functions' error when exporting non-async/cache functions about next.js HOT 6 CLOSED

The issue is caused by the stricter use server check in the recent 14.1.2 update, it seems to me NextJS is performing syntax-level checking which might raise some false errors. It actually breaks my server action builder package.

Repro: https://github.com/chungweileong94/next-use-server-bug

from next.js.

Its worth noting that this currently breaks the example shown in the documentation around using React.cache currently: https://nextjs.org/docs/app/building-your-application/data-fetching/fetching-caching-and-revalidating#fetching-data-on-the-server-with-third-party-libraries

from next.js.

yeah, i had to make sure i used the export async function(return somepromise) syntax, as export const = async () => { await ... } would not work

from next.js.

It seems like NextJS is doing action.constructor.name !== 'AsyncFunction' check, however, if the action is created via a library, it will get transpiled into Promise<...> instead of action.constructor.name !== 'AsyncFunction'. The only workaround now is to create a async function wrapper around, which is kinda annoying.

from next.js.

This is a duplicate of #62860 - please give #62860 (comment) and #62821 a read. We'll keep everyone updated there.

Basically it does not make sense to use React.cache together with Server Actions and it will not cache anything.

from next.js.

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

from next.js.