servermiddleware -- config vars

[34r7h]

Please document the proper configuration for now.json, nuxt.config.js, and env on vercel. Nuxt app renders fine. /api/ gives various errors, 405, 500, and my favorite is the 200 with html when the env spits out domain.com/domain/.com. I've tried hundreds of variations and just don't get it.

nuxt.config.js
serverMiddleware: [{ path: '/api/', handler: '~/server-middleware/index' }], axios: { baseURL: process.env.HOST || 'http://localhost:3000' },

now.json
{ "version": 2, "builds": [ { "src": "nuxt.config.js", "use": "@nuxtjs/vercel-builder", "config": { "serverFiles": [ "server-middleware/**" ] } } ] }

.vue
methods: { api(type, args) { return this.$axios.post('/api/'+type, args).then((x) => { console.log(x); return this.$set(this.apireturns, type, x.data); }); }, },

server-middleware/index.js
export default app.use(async function (req, res) { if (req.url.replace('/', '') === '') return res.end(JSON.stringify('No method provided')); let meth = req.url.replace('/', '') if (meth == 'encode') { let ret = methods.encode(req.body) ret.map(x => JSON.stringify(x)) return res.end(JSON.stringify(ret)); }

[danielroe]

@34r7h Would you be able to provide a reproduction?

[danielroe]

Environment variables work exactly how you might expect, with this proviso about how Nuxt embeds environment variables at build-time - this section of the docs is a must read.

If you set environment variables through the Vercel dashboard - such as a system environment variable - then it only needs to be configured in your project settings, and it will be made available at both build and run-time.

You will then be able to access this variable from process.env just as though it was a normal environment variable.

Feel free to inspect the logs and source code of the following deployment I have created to show this at work:

• Live site
• Logs
• Source