Daniel Roe
Daniel Roe
I'm not quite sure we'd want to support this usage. We do however support auto-discovery of additional routes via adding them via the `x-nitro-prerender` header, and might consider adding a...
Are you sure that's the content of the file? No stray comma? How about your `tsconfig.json`?
You likely need to use a newer Node runtime in your vercel project.
You should now be able to use Node 16 with @nuxtjs/[email protected]. Let me know if not and we can reopen.
Would you provide a reproduction? 🙏
You can see it working fine in stackblitz ([here](https://stackblitz.com/edit/github-3nzgrn?file=index.mjs)). It also works fine for me locally.  Are you getting this locally, or just in...
Yes - confirmed. You need features from TS 4.7+; versions below that show this error.
@tim3trick No need to do anything. For now you can use a newer version of TypeScript. I'll keep this open until I've had a chance to see whether it's possible...
The Nuxt 3 issue in the stackblitz above is caused by the polyfill being stripped from the final build output, likely for the same cause as https://github.com/nuxt/nuxt.js/issues/13152.
That seems good to me; wdyt @atinux?