You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This happens because of how we transform "use server" modules to wrap exports to register server-side actions. We need to either fix this, or if it makes sense to keep the restriction, catch it and provide understandable error message about what happened, how to fix it, and why it needs to be that way.
The text was updated successfully, but these errors were encountered:
We currently have an issue with `"use server"` modules where we cannot use `export default`s, only `export`s.
This PR avoids the issue by changing the relevant `export default`s to `export`s. #84 tracks solving the actual issue for future cases.
We currently have an issue with `"use server"` modules where we cannot use `export default`s, only `export`s.
This PR avoids the issue by changing the relevant `export default`s to `export`s. #84 tracks solving the actual issue for future cases.
When using "use server", you're able to
export
, but notexport default
. Otherwise you'll see this when youpnpm build
This happens because of how we transform "use server" modules to wrap exports to register server-side actions. We need to either fix this, or if it makes sense to keep the restriction, catch it and provide understandable error message about what happened, how to fix it, and why it needs to be that way.
The text was updated successfully, but these errors were encountered: