feat: add nuxt example

[posva]

The PR has a working minimal nuxt example but uses pnpm and has a pnpm-lock.yaml file. Also it uses the locally built zero-native (from ../..)

I had a hard time running the examples locally with npm, so I switched to pnpm which worked out fine. The example uses the locally built binary but I think you use the examples as templates for zero-native init my-app --frontend ..., so this is just a draft at the moment.

I did try to follow CONTRIBUTING.md but it wasn't enough for me to get started with the project.

In case it's relevant, I get these errors from npm i --prefix frontend:

~/o/v/z/e/react ❯❯❯ zig build run
npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: react@0.1.0
npm error Found: vite@undefined
npm error node_modules/vite
npm error   dev vite@"^8.0.11" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^8.0.0" from @vitejs/plugin-react@6.0.1
npm error node_modules/@vitejs/plugin-react
npm error   dev @vitejs/plugin-react@"^6.0.1" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.

[vercel]

@posva is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[posva]

I couldn't get npm to work on any of the examples but I bet that's just an issue on my end

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​vue-router@​5.0.6
	npm/​nuxt@​4.4.5

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm entities is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: examples/nuxt/frontend/pnpm-lock.yaml → npm/nuxt@4.4.5 → npm/entities@4.5.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/entities@4.5.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm ioredis is 96.0% likely obfuscated Confidence: 0.96 Location: Package overview From: examples/nuxt/frontend/pnpm-lock.yaml → npm/nuxt@4.4.5 → npm/ioredis@5.10.1 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/ioredis@5.10.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report