Unable to start the server.
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- bun, typescript
- Domain
- developer-experience
Research direction
Start with the setup steps in README.md and reproduce the failure using bun install followed by bun dev. Use the linked screenshot to identify the reported error, then verify whether the documented setup is incomplete; done means the server starts successfully or README.md clearly documents the required steps.
Written by the indexing model from the issue text.
Description
Bug description
I followed the steps in the README.md file:
- Ran
bun install - Ran
bun dev
However, the server isn't running, and I encountered an error (see the screenshot below).
I am unsure whether this is an issue with the setup or if I'm missing something. If this issue is irrelevant, feel free to close it.
Here’s how you can open the issue based on your provided details, formatted to look like a GitHub issue:
Title: Issue with Running Server Using bun dev
Bug description:
I followed the steps in the README.md file:
Ran bun install
Ran bun dev
However, the server isn't running, and I encountered an error (see the screenshot below).
I am unsure whether this is an issue with the setup or if I'm missing something. If this issue is irrelevant, feel free to close it.
Screenshot:
How to reproduce
bun installbun dev
Expected Behavior:
The server should start successfully after running the above commands.
##Actual Behavior:
The server fails to start, and the error shown in the screenshot appears.
Additional context
is there any other method then please update your readme.md file so that every open source developer will contribute.
- Dominant language
- TypeScript
- Stars
- 29k
- Forks
- 4k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 71
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from GitbookIO/gitbook
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 55/100
All issues in GitbookIO/gitbook
Similar issues
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P3
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 76/100
-
code-quality refactoring
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
vercel/react-tweet#225 ·