[Module Listing Request]: `nuxt-safe-action`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 1.1k
- Forks
- 354
- Avg merge
- 10h 18m
- Merged PRs (30d)
- 12
Description
Description
Server actions for Nuxt with end-to-end type safety. You define actions in server/actions/ using a builder chain with Zod validation and middleware, and the module generates typed client references automatically. Comes with a useAction composable that gives you reactive status, field-level validation errors, and callbacks. Basically https://github.com/TheEdoRan/next-safe-action but for Nuxt, with H3Event access and auto route generation.
Repository
https://github.com/rutbergphilip/nuxt-safe-action
npm
https://www.npmjs.com/package/nuxt-safe-action
Nuxt Compatibility
Nuxt 4, Nuxt 3
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No target file, test, or entry point is named. Start by reviewing the Nuxt modules repository's existing catalog entries and contribution workflow, then use the linked nuxt-safe-action repository and npm package to determine the metadata needed for a listing. Done means the module is represented consistently in the catalog.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nuxt
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100