max-mapper / max-mapper/websocket-stream
what to do when WS is not a constructor?
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 667
- Forks
- 110
- PR merge metrics
- No merged PRs in 30d
Description
for some exotic browsers i want to support, like opera, i see the WS is not a constructor error.
do you think you could add a workaround for that? if not, what else would you suggest in my place?
Contributor guide
No contributing guide indexed for this repository
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
The issue names no files, tests, or entry points. Start by reproducing the WS is not a constructor error in Opera or another affected browser, then trace where the WebSocket constructor is selected; done means an agreed compatibility workaround or a documented alternative.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100