@vercel/next 3.4.3 → 3.4.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/dist/index.js CHANGED
@@ -43768,11 +43768,7 @@ async function getRoutesManifest(entryPath, outputDirectory, nextVersion) {
43768
43768
  .catch(() => false);
43769
43769
  if (shouldHaveManifest && !hasRoutesManifest) {
43770
43770
  throw new build_utils_1.NowBuildError({
43771
- message: `The file "${pathRoutesManifest}" couldn't be found. This is normally caused by a misconfiguration in your project.\n` +
43772
- 'Please check the following, and reach out to support if you cannot resolve the problem:\n' +
43773
- ' 1. If present, be sure your `build` script in "package.json" calls `next build`.' +
43774
- ' 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`.' +
43775
- ' 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.',
43771
+ message: `The file "${pathRoutesManifest}" couldn't be found. This is often caused by a misconfiguration in your project.`,
43776
43772
  link: 'https://err.sh/vercel/vercel/now-next-routes-manifest',
43777
43773
  code: 'NEXT_NO_ROUTES_MANIFEST',
43778
43774
  });
package/dist/utils.js CHANGED
@@ -166,11 +166,7 @@ async function getRoutesManifest(entryPath, outputDirectory, nextVersion) {
166
166
  .catch(() => false);
167
167
  if (shouldHaveManifest && !hasRoutesManifest) {
168
168
  throw new build_utils_1.NowBuildError({
169
- message: `The file "${pathRoutesManifest}" couldn't be found. This is normally caused by a misconfiguration in your project.\n` +
170
- 'Please check the following, and reach out to support if you cannot resolve the problem:\n' +
171
- ' 1. If present, be sure your `build` script in "package.json" calls `next build`.' +
172
- ' 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`.' +
173
- ' 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.',
169
+ message: `The file "${pathRoutesManifest}" couldn't be found. This is often caused by a misconfiguration in your project.`,
174
170
  link: 'https://err.sh/vercel/vercel/now-next-routes-manifest',
175
171
  code: 'NEXT_NO_ROUTES_MANIFEST',
176
172
  });
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@vercel/next",
3
- "version": "3.4.3",
3
+ "version": "3.4.4",
4
4
  "license": "MIT",
5
5
  "main": "./dist/index",
6
6
  "homepage": "https://vercel.com/docs/runtimes#official-runtimes/next-js",
@@ -11,7 +11,7 @@
11
11
  "test-unit": "pnpm test test/unit/",
12
12
  "test-next-local": "pnpm test test/integration/*.test.js test/integration/*.test.ts",
13
13
  "test-next-local:middleware": "pnpm test test/integration/middleware.test.ts",
14
- "test-integration-once": "rm -f test/builder-info.json; pnpm test test/fixtures/**/*.test.js"
14
+ "test-e2e": "rm -f test/builder-info.json; pnpm test test/fixtures/**/*.test.js"
15
15
  },
16
16
  "repository": {
17
17
  "type": "git",
@@ -45,7 +45,7 @@
45
45
  "@types/semver": "6.0.0",
46
46
  "@types/text-table": "0.2.1",
47
47
  "@types/webpack-sources": "3.2.0",
48
- "@vercel/build-utils": "6.2.2",
48
+ "@vercel/build-utils": "6.2.3",
49
49
  "@vercel/nft": "0.22.5",
50
50
  "@vercel/routing-utils": "2.1.8",
51
51
  "async-sema": "3.0.1",
@@ -71,5 +71,5 @@
71
71
  "typescript": "4.5.2",
72
72
  "webpack-sources": "3.2.3"
73
73
  },
74
- "gitHead": "95a4dcfb33d813f1a0ef18d766232d42c876ce69"
74
+ "gitHead": "881e43a0e2d6daa2f7654ad16566960b00d412aa"
75
75
  }