Confusing Documentation on Fresh Websocket
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 55/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- deno, typescript
- Domain
- backend, documentation
Research direction
Read the Fresh WebSocket development documentation and check the version guidance against available Fresh releases. Then clarify how to run a separate Deno entry point alongside Vite, including a concrete setup example; done when the release guidance is accurate and a newcomer can test WebSocket changes without rebuilding each time.
Written by the indexing model from the issue text.
Description
First off, I am new to fresh and deno, but I really like it. I am considering using this for next big project.
One of the issues is getting fresh setup with Websockets. The documentation says this:
WebSocket upgrades under the Vite dev server (deno task dev) require Fresh 2.4+ and Deno 2.8+. On older versions Deno.upgradeWebSocket() cannot complete the 101 handshake for requests Vite forwards from its Node HTTP server, so ctx.upgrade() and app.ws() silently hang and the open handler is never invoked.
My problem is that Fresh 2.4+ does not seem to exist yet (is there a plan to release it soon)?
My second issue is with the last half of the documentation:
Alternatively, run a separate Deno entry point (e.g. deno serve -A main.ts) alongside Vite, or host the WebSocket server as a sidecar on its own port.
It is not clear to me that I am doing this right. Documentation is sparse.
Is it possible to get the websocket dev setup so I do not have to rebuild e verytime i want to test changes in my websocket code?
- Dominant language
- TypeScript
- Stars
- 13.8k
- Forks
- 757
- Avg merge
- 3m
- Merged PRs (30d)
- 2
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 freshframework/fresh
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
freshframework/fresh#3920 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
freshframework/fresh#3833 ·
-
feat
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
freshframework/fresh#3803 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 10/100
freshframework/fresh#3918 · 1 comment · 4 reactions ·
-
Tab title doesn't update to <Head> <title> when navigating to a page with another <title>Possibly taken @1AbdullahButt claimed this 7 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 57/100
freshframework/fresh#3916 ·
All issues in freshframework/fresh
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
tintinweb/pi-subagents#459 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
danielmiessler/LifeOS#2830 ·
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
area: client enhancement priority: low
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opensro-dev/opensro#3681 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day