Error in vercel deploy: TypeError: Cannot read properties of undefined (reading 'v2_meta')

[Lucas-Eduardo-Goncalves]

What version of Remix are you using?

1.6.7

Steps to Reproduce

clone repository by ssh: git clone git@github.com:Lucas-Eduardo-Goncalves/pac.app.git
then add this repository to vercel, and try.

Expected Behavior

My site should work normally. On localhost I can't find it works normally.

Actual Behavior

I find the error message: TypeError: Cannot read properties of undefined (reading 'v2_meta')

[meglio]

Same error for me in 1.8.0. Wasn't a case with 1.7.2

[machour]

Can you add future: {} in your remix.config.js and see if the issue goes away?

[antoninbeaufort]

Had the same problem but adding future: {} solved the problem

[ThanhPhat1080]

Seem you are missing edit the remix config while you want to deploy to Vercel.
In remix.config.js

/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  serverBuildTarget: "vercel",
  // When running locally in development mode, we use the built in remix
  // server. This does not understand the vercel lambda module format,
  // so we default back to the standard build output.
  server: process.env.NODE_ENV === "development" ? undefined : "./server.js",
  ignoredRouteFiles: ["**/.*"],
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "api/index.js",
  // publicPath: "/build/",
};

Create new server.js file at your root folder (the same level of remix.config.js)

import { createRequestHandler } from "@remix-run/vercel";
import * as build from "@remix-run/dev/server-build";

export default createRequestHandler({ build, mode: process.env.NODE_ENV });

[sjwinther]

Having the same problem, but adding future: {} does not solve the issue. I already have a server.js file as described by @ThanhPhat1080.

[machour]

@sjwinther are all your remix deps on 1.8.0? Can you share a gist of your package.json depedencies & devDependencies sections?

[sjwinther]

@machour Yup! Here you go: https://gist.github.com/sjwinther/643603e3c40273614f05855ff2ce90db

[machour]

@sjwinther just to confirm, you're seeing Cannot read properties of undefined (reading 'v2_meta') even tho you added future: {} to your remix.config.js file? (Please update the gist with its contents 🙏)

[sjwinther]

Looks like I got it resolved now, although it was pretty difficult to figure out from the error. I was returning { rel: "icon", href: "/favicon.png", type: "image/png" } in one of the Link functions and for some reason Remix didn't like that? I was getting this error as well, both errors disappeared when I removed the favicon.png link:

{
  data: 'No route matches URL "/favicon.ico"',
  status: 404,
  statusText: 'Not Found'
}
No routes matched location "/favicon.ico"

[AnthonyLzq]

Seem you are missing edit the remix config while you want to deploy to Vercel. In remix.config.js

/** @type {import('@remix-run/dev').AppConfig} */
module.exports = {
  serverBuildTarget: "vercel",
  // When running locally in development mode, we use the built in remix
  // server. This does not understand the vercel lambda module format,
  // so we default back to the standard build output.
  server: process.env.NODE_ENV === "development" ? undefined : "./server.js",
  ignoredRouteFiles: ["**/.*"],
  // appDirectory: "app",
  // assetsBuildDirectory: "public/build",
  // serverBuildPath: "api/index.js",
  // publicPath: "/build/",
};

Create new server.js file at your root folder (the same level of remix.config.js)

import { createRequestHandler } from "@remix-run/vercel";
import * as build from "@remix-run/dev/server-build";

export default createRequestHandler({ build, mode: process.env.NODE_ENV });

This solution worked for me, in addition to adding the property future: {}. Besides I have installed @remix-run/vercel and @vercel/node according to @sjwinther 's gist.

[TheGreatRambler]

I'm also running into this issue with

		"@remix-run/node": "^1.7.2",
		"@remix-run/react": "^1.7.2",
		"@remix-run/serve": "^1.7.2",