@vercel/next 3.4.3 → 3.4.4

package/dist/index.js

@@ -43768,11 +43768,7 @@ async function getRoutesManifest(entryPath, outputDirectory, nextVersion) {
         .catch(() => false);
     if (shouldHaveManifest && !hasRoutesManifest) {
         throw new build_utils_1.NowBuildError({
-            message: `The file "${pathRoutesManifest}" couldn't be found. This is normally caused by a misconfiguration in your project.\n` +
-                'Please check the following, and reach out to support if you cannot resolve the problem:\n' +
-                '  1. If present, be sure your `build` script in "package.json" calls `next build`.' +
-                '  2. Navigate to your project\'s settings in the Vercel dashboard, and verify that the "Build Command" is not overridden, or that it calls `next build`.' +
-                '  3. Navigate to your project\'s settings in the Vercel dashboard, and verify that the "Output Directory" is not overridden. Note that `next export` does **not** require you change this setting, even if you customize the `next export` output directory.',
+            message: `The file "${pathRoutesManifest}" couldn't be found. This is often caused by a misconfiguration in your project.`,
             link: 'https://err.sh/vercel/vercel/now-next-routes-manifest',
             code: 'NEXT_NO_ROUTES_MANIFEST',
         });

package/dist/utils.js

@@ -166,11 +166,7 @@ async function getRoutesManifest(entryPath, outputDirectory, nextVersion) {
         .catch(() => false);
     if (shouldHaveManifest && !hasRoutesManifest) {
         throw new build_utils_1.NowBuildError({
-            message: `The file "${pathRoutesManifest}" couldn't be found. This is normally caused by a misconfiguration in your project.\n` +
-                'Please check the following, and reach out to support if you cannot resolve the problem:\n' +
-                '  1. If present, be sure your `build` script in "package.json" calls `next build`.' +
-                '  2. Navigate to your project\'s settings in the Vercel dashboard, and verify that the "Build Command" is not overridden, or that it calls `next build`.' +
-                '  3. Navigate to your project\'s settings in the Vercel dashboard, and verify that the "Output Directory" is not overridden. Note that `next export` does **not** require you change this setting, even if you customize the `next export` output directory.',
+            message: `The file "${pathRoutesManifest}" couldn't be found. This is often caused by a misconfiguration in your project.`,
             link: 'https://err.sh/vercel/vercel/now-next-routes-manifest',
             code: 'NEXT_NO_ROUTES_MANIFEST',
         });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@vercel/next",
-  "version": "3.4.3",
+  "version": "3.4.4",
   "license": "MIT",
   "main": "./dist/index",
   "homepage": "https://vercel.com/docs/runtimes#official-runtimes/next-js",
@@ -11,7 +11,7 @@
     "test-unit": "pnpm test test/unit/",
     "test-next-local": "pnpm test test/integration/*.test.js test/integration/*.test.ts",
     "test-next-local:middleware": "pnpm test test/integration/middleware.test.ts",
-    "test-integration-once": "rm -f test/builder-info.json; pnpm test test/fixtures/**/*.test.js"
+    "test-e2e": "rm -f test/builder-info.json; pnpm test test/fixtures/**/*.test.js"
   },
   "repository": {
     "type": "git",
@@ -45,7 +45,7 @@
     "@types/semver": "6.0.0",
     "@types/text-table": "0.2.1",
     "@types/webpack-sources": "3.2.0",
-    "@vercel/build-utils": "6.2.2",
+    "@vercel/build-utils": "6.2.3",
     "@vercel/nft": "0.22.5",
     "@vercel/routing-utils": "2.1.8",
     "async-sema": "3.0.1",
@@ -71,5 +71,5 @@
     "typescript": "4.5.2",
     "webpack-sources": "3.2.3"
   },
-  "gitHead": "95a4dcfb33d813f1a0ef18d766232d42c876ce69"
+  "gitHead": "881e43a0e2d6daa2f7654ad16566960b00d412aa"
 }