vercel deploy --prebuilt fails with Builder returned invalid routes

[jimkyndemeyer]

Hey,

I'm building a Next.js project with vercel build and then trying to deploy it with vercel deploy --prebuilt, but the last step fails with:

[11:05:08.789] Retrieving list of deployment files...
[11:05:11.929] Downloading 32 deployment files...
[11:05:13.803] Using prebuilt build artifacts...
[11:05:14.550] Error: Builder returned invalid routes: ["Route at index 5 has invalid `src` regular expression \"^\\_next\\data\\(.*)$\".","Route at index 9 has invalid `src` regular expression \"^\\_next\\static\\(?:[^\\]+\\pages|pages|chunks|runtime|css|image|media)\\.+$\".","Route at index 11 has invalid `src` regular expression \"^\\_next\\data\\(.*)$\".","Route at index 14 has invalid `src` regular expression \"^\\_next\\static\\(?:[^\\]+\\pages|pages|chunks|runtime|css|image|media|ZbXeqU5AKFqd_XwtmAIEU)\\.+$\".","Route at index 16 has invalid `src` regular expression \"^\\((?!index$).*)$\"."]

Using latest versions -- Next.js 12.2.3 and Vercel 27.2.0.

Any ideas how to resolve this? It's a super small project I just started, with the following routes:

[amyegan]

Hi @jimkyndemeyer. Do you have any custom route rewrites or redirects set up in a vercel.json or next.config.js file? Or is routing being handled entirely by Next automatically?

[jimkyndemeyer]

No vercel.json file, and my next.config.js is as follows:

// @ts-check
const {createVanillaExtractPlugin} = require('@vanilla-extract/next-plugin');
const withPlugins = require('next-compose-plugins');

const withVanillaExtract = createVanillaExtractPlugin();

const withTM = require('next-transpile-modules')([
    '@project/components'
]);


/**
 * @type {import('next').NextConfig}
 */
const nextConfig = {
}

module.exports = withPlugins([
    withVanillaExtract(withTM(nextConfig)),
]);

Should the [...nextauth].ts route which spreads params work with this kind of deploy?

[amyegan]

I couldn't reproduce the issue by adding NextAuth with the [...nextauth].js route in my own project. Are you able to share the repo you're using so I can take a closer look?

[jimkyndemeyer]

Thanks for taking a look.

It's part of a mono-repo that I can't share, but I'll see if I can extract out a stand-alone version that reproduces the issue :)