We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug hit below error, with basehub api token configured too.
┌ @repo/cms#dev > cache bypass, force executing d8079bd25888d5d7 │ │ > @repo/[email protected] dev /Volumes/newVolumes/go/src/github.com/Axpz/catx9/packages/cms │ > basehub dev │ │ TypeError: fetch failed │ at node:internal/deps/undici/undici:13392:13 │ at process.processTicksAndRejections (node:internal/process/task_queues:105:5) { │ [cause]: ConnectTimeoutError: Connect Timeout Error │ at onConnectTimeout (/Volumes/newVolumes/go/src/github.com/Axpz/catx9/node_modul │ es/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:186:24) │ at /Volumes/newVolumes/go/src/github.com/Axpz/catx9/node_modules/.pnpm/undici@5. │ 28.4/node_modules/undici/lib/core/connect.js:133:46 │ at Immediate._onImmediate (/Volumes/newVolumes/go/src/github.com/Axpz/catx9/node │ _modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:174:9) │ at process.processImmediate (node:internal/timers:491:21) { │ code: 'UND_ERR_CONNECT_TIMEOUT' │ } │ } │ ELIFECYCLE Command failed with exit code 1. │ command finished with error: command (/Volumes/newVolumes/go/src/github.com/Axpz/catx9 │ /packages/cms) /usr/local/bin/pnpm run dev exited (1) next-forge version 2.21.11
To Reproduce Steps to reproduce the behavior: a regular setup and.
Expected behavior the demo can running as expected.
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
hit below error, with basehub api token configured too.
┌ @repo/cms#dev > cache bypass, force executing d8079bd25888d5d7
│
│ > @repo/[email protected] dev /Volumes/newVolumes/go/src/github.com/Axpz/catx9/packages/cms
│ > basehub dev
│
│ TypeError: fetch failed
│ at node:internal/deps/undici/undici:13392:13
│ at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
│ [cause]: ConnectTimeoutError: Connect Timeout Error
│ at onConnectTimeout (/Volumes/newVolumes/go/src/github.com/Axpz/catx9/node_modul
│ es/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:186:24)
│ at /Volumes/newVolumes/go/src/github.com/Axpz/catx9/node_modules/.pnpm/undici@5.
│ 28.4/node_modules/undici/lib/core/connect.js:133:46
│ at Immediate._onImmediate (/Volumes/newVolumes/go/src/github.com/Axpz/catx9/node
│ _modules/.pnpm/[email protected]/node_modules/undici/lib/core/connect.js:174:9)
│ at process.processImmediate (node:internal/timers:491:21) {
│ code: 'UND_ERR_CONNECT_TIMEOUT'
│ }
│ }
│ ELIFECYCLE Command failed with exit code 1.
│ command finished with error: command (/Volumes/newVolumes/go/src/github.com/Axpz/catx9
│ /packages/cms) /usr/local/bin/pnpm run dev exited (1)
next-forge version
2.21.11
To Reproduce
Steps to reproduce the behavior:
a regular setup and.
Expected behavior
the demo can running as expected.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: