GitbookIO / GitbookIO/integrations
Hot Reloading through gitbook dev command not working reliably
Open
Nobody has claimed this yet.
cli
- Dominant language
- TypeScript
- Stars
- 131
- Forks
- 96
- Avg merge
- 7h 8m
- Merged PRs (30d)
- 31
Description
When using the gitbook dev <space_id> command from the @gitbook/cli, I've found that hot reloading doesn't work reliably.
Hard reloads to the browser page / space helps, when the cache is disabled. Figuring out a better way to get the page/components to hot reload would make developing integration UI quicker 👌
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.
Research direction
Start by reproducing the issue with the @gitbook/cli gitbook dev <space_id> command, observing hot reload behavior in the browser with and without cache disabled. Trace the dev command's reload path and verify that page and component changes update reliably without requiring a hard reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli, developer-experience, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100