squarecylinder
commented
4 years ago I can't seem to get the same errors as you, however I can't get a successful build either.
Running npm run dev prints out
> next-vanture@0.1.0 dev C:\Users\amber\Desktop\opensource_help\vantures
> next dev -p 8080
ready - started server on http://localhost:8080
event - compiled successfully
event - build page: /api/results
wait - compiling...
event - compiled successfully
(node:28452) UnhandledPromiseRejectionWarning: RangeError [ERR_HTTP_INVALID_STATUS_CODE]: Invalid status code: ENOTFOUND
at ServerResponse.writeHead (_http_server.js:249:11)
at ServerResponse.writeHead (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\next\dist\compiled\compression\index.js:1:144825)
at ServerResponse._implicitHeader (_http_server.js:240:8)
at ServerResponse.end (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\next\dist\compiled\compression\index.js:1:148771)
at onerror (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\next-connect\lib\index.js:5:7)
at next (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\next-connect\lib\index.js:66:13)
at next (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\next-connect\lib\index.js:68:19)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:28452) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:28452) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.Running npm run build prints out
> next-vanture@0.1.0 build C:\Users\amber\Desktop\opensource_help\vantures
> next build
Creating an optimized production build
Compiled successfully.
> Build error occurred
Error [FetchError]: request to http://localhost:8080/api/results failed, reason: read ECONNRESET
at ClientRequest.<anonymous> (C:\Users\amber\Desktop\opensource_help\vantures\node_modules\isomorphic-fetch\node_modules\node-fetch\index.js:133:11)
at ClientRequest.emit (events.js:314:20)
at Socket.socketErrorListener (_http_client.js:469:9)
at Socket.emit (events.js:314:20)
at emitErrorNT (internal/streams/destroy.js:100:8)
at emitErrorCloseNT (internal/streams/destroy.js:68:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
type: 'system',
errno: 'ECONNRESET',
code: 'ECONNRESET'
}
Automatically optimizing pages .npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! next-vanture@0.1.0 build: `next build`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the next-vanture@0.1.0 build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\amber\AppData\Roaming\npm-cache\_logs\2020-08-04T17_52_13_075Z-debug.logThis is what the logs show
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\\Program Files\\nodejs\\node.exe',
1 verbose cli 'C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js',
1 verbose cli 'run',
1 verbose cli 'build'
1 verbose cli ]
2 info using npm@6.14.5
3 info using node@v14.5.0
4 verbose run-script [ 'prebuild', 'build', 'postbuild' ]
5 info lifecycle next-vanture@0.1.0~prebuild: next-vanture@0.1.0
6 info lifecycle next-vanture@0.1.0~build: next-vanture@0.1.0
7 verbose lifecycle next-vanture@0.1.0~build: unsafe-perm in lifecycle true
8 verbose lifecycle next-vanture@0.1.0~build: PATH: C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin;C:\Users\amber\Desktop\opensource_help\vantures\node_modules\.bin;C:\Program Files\Git\mingw64\bin;C:\Program Files\Git\usr\bin;C:\Users\amber\bin;C:\Python38\Scripts;C:\Python38;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\iCLS;C:\Program Files\Intel\Intel(R) Management Engine Components\iCLS;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem;C:\WINDOWS\System32\WindowsPowerShell\v1.0;C:\WINDOWS\System32\OpenSSH;C:\Program Files\Intel\WiFi\bin;C:\Program Files\Common Files\Intel\WirelessCommon;C:\Program Files (x86)\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Intel\Intel(R) Management Engine Components\DAL;C:\Program Files\Git\cmd;C:\Program Files\MongoDB\Server\4.2\bin;C:\Program Files\nodejs;C:\ProgramData\chocolatey\bin;C:\Users\amber\AppData\Local\Microsoft\WindowsApps;C:\Users\amber\AppData\Local\Programs\Microsoft VS Code\bin;C:\Users\amber\AppData\Local\GitHubDesktop\bin;C:\Program Files\heroku\bin;C:\Users\amber\AppData\Local\Microsoft\WindowsApps;C:\Users\amber\AppData\Roaming\npm
9 verbose lifecycle next-vanture@0.1.0~build: CWD: C:\Users\amber\Desktop\opensource_help\vantures
10 silly lifecycle next-vanture@0.1.0~build: Args: [ '/d /s /c', 'next build' ]
11 silly lifecycle next-vanture@0.1.0~build: Returned: code: 1 signal: null
12 info lifecycle next-vanture@0.1.0~build: Failed to exec build script
13 verbose stack Error: next-vanture@0.1.0 build: `next build`
13 verbose stack Exit status 1
13 verbose stack at EventEmitter.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:314:20)
13 verbose stack at ChildProcess.<anonymous> (C:\Program Files\nodejs\node_modules\npm\node_modules\npm-lifecycle\lib\spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:314:20)
13 verbose stack at maybeClose (internal/child_process.js:1051:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:287:5)
14 verbose pkgid next-vanture@0.1.0
15 verbose cwd C:\Users\amber\Desktop\opensource_help\vantures
16 verbose Windows_NT 10.0.18363
17 verbose argv "C:\\Program Files\\nodejs\\node.exe" "C:\\Program Files\\nodejs\\node_modules\\npm\\bin\\npm-cli.js" "run" "build"
18 verbose node v14.5.0
19 verbose npm v6.14.5
20 error code ELIFECYCLE
21 error errno 1
22 error next-vanture@0.1.0 build: `next build`
22 error Exit status 1
23 error Failed at the next-vanture@0.1.0 build script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]
Other things to note, I was never able to get the mongodb collection showing up either. System information
- OS: Microsoft Windows 10 Home Version 10.0.18363 Build 18363
- node v14.5.0
- next v9.5.1
saswatamcode
itsclarke
AlexRAV
jscardona12
Oxicode
touqeeraslam
gusilveiramp
chankruze
vihapr
Immortal000
karthik-js
rubenscorrea20
deniercounter
codeGTI
Aiglobelam
aliazimoshan
Bug report
Describe the bug
I have a fairly simple app that pings a mongo database and generates dynamic pages. The homepage lists a handful of documents and they link to individual pages. The build often fails complaining about missing modules despite running perfectly fine on localhost. However, if I build it a 2nd or 3rd time it will usually succeed.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:
npm run devnpm run buildExpected behavior
A failed build outputs:
When it succeeds the build outputs:
But the other server running the API code outputs this as well:
System information