Environment clarification for Vercel API Route

[rtritto]

Is the vike-with-vercel example only for development usage (only dev script in vike-with-vercel/package.json)?

• If yes, the Vercel API Route doc should be updated with the reference of only development usage.
• If no, vike-with-vercel should also provide a production example (maybe simple add a production section script in vike-with-vercel/package.json)

[brillout]

https://github.com/brillout/vike-with-vercel#readme
brillout/vike-with-vercel@94c9feb
https://brillout.github.io/rules/#try

[rtritto]

vike-with-vercel seems to be a basic usage for development (no dist/server directory to Vercel output directory).

---

For production with server should be:

• • Modify Build and Output Settings > OUTPUT DIRECTORY from dist to dist/client.

  This step isn't needed: OUTPUT DIRECTORY needs to remain dist (default) to also include dist/client and dist/server

• Use "dev": "NODE_ENV=production node dist/server/index.mjs" script

[brillout]

No, IIRC OUTPUT DIRECTORY is the directory of static assets.

Also, no, the repo showcases using Vite for dev, as stated in the repo's package.json.

That said, our upcoming vike-vercel integation will work more like what you expect.

Please be more thoughtful before reaching out with suggestions. It's what I told you before: please trust us that we know what we're doing. It's much more productive if you reach out with concrete problems, instead of reaching out with "you think is the best solution". Only maintainers can design solutions (because only maintainers understand the whole problem space in a holistic manner). I told you that already, so please respect that. Thank you.

Kind regards.