Skip to content

basehub graphql api is stopping app from spinning up locally #476

New issue

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

Open
DaveMitten opened this issue Mar 8, 2025 · 1 comment
Open

basehub graphql api is stopping app from spinning up locally #476

DaveMitten opened this issue Mar 8, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@DaveMitten
Copy link

DaveMitten commented Mar 8, 2025

Describe the bug
When spinning up the local env. Since the most recent update to basehub, the graphql endpoint is now returning a 500 bad request.

next-forge version
I am using version ...

To Reproduce
Steps to reproduce the behavior:

  1. Spin up locally

Expected behavior
App runs locally.

Screenshots
If applicable, add screenshots to help explain your problem.

Image

terminal read out:

 @repo/cms#dev > cache bypass, force executing 2187781b3184f7dc 
│ 

│ > basehub dev
│ 
│ 🪄 Generating...
│ ┌─────────────────────────────────────────────────────────────────────────────────
│ ─────────────────────┐
│ │ 🎫 SDK Version: 8.1.13                                                          
│                      │
│ │ 🔗 Endpoint: https://api.basehub.com/graphql                                    
│                      │
│ │ 🟡 Draft: enabled                                                               
│                      │

│ │ 🔀 Ref: main (basehub branch)                                                   
│                      │
│ └─────────────────────────────────────────────────────────────────────────────────
│ ─────────────────────┘

│   ✖ introspection for https://api.basehub.com/graphql failed, 500 Internal
│     Server Error
│   ◼ preparing client directory
│   ◼ writing files
│ Unhandled Rejection at: Promise { <rejected> undefined } reason: undefined
│ 
│ 👋 Stopped `basehub` watcher.
│  ELIFECYCLE  Command failed with exit code 1.
│ command finished with error: command
│  exited (1)
└────>
@repo/cms#dev: command 

 Tasks:    0 successful, 8 total
Cached:    0 cached, 8 total
  Time:    2.792s 
Failed:    @repo/cms#dev

 ERROR  run failed: command  exited (1)
 ELIFECYCLE  Command failed with exit code 1.

**Desktop (please complete the following information):**
 - OS: [e.g. MacOS] macOS
 - Browser arc and safari
@DaveMitten DaveMitten added the bug Something isn't working label Mar 8, 2025
@DaveMitten
Copy link
Author

Ideally we need a. way to bypass issues like this, this is the 3rd time in a month I am unable to work on or use the project with next-forge due to something failing when running the dev environment or build process.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant